Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    “Error c0528 inv-a 35” “Remote Service Error, Could not write new budget info.”

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Our Technical Services Librarian has reported a problem we have not experienced before in the ACQ module processing large invoices. When adding orders to the invoice the first 8 orders are added properly, with the budget added and the cost moved from encumbered to expended. On the 9th order (the order number used does not matter) Aleph ceases this normal behavior. The budget used (BK-GENERAL-2011) for the order does not display and the cost is not expended but merely remains encumbered.

    If you try to manually add the budget, from within the Order Info area of the Invoice tab, Aleph reports the error message “Error c0528 inv-a 35” “Remote Service Error, Could not write new budget info.”. The library routinely processes invoices of this size, from this same vendor and others. The system continues to process smaller invoices without issue.

    When reported to me, I attempted to duplicate the problem in our Aleph Test instance. The issue does not occur in Test. Test’s data is approximately 1 month old compared to Production.

    I reviewed the vendor, the budget and its parent/grandparent, the invoice and orders. The only one difference I could find between Test and Production was that the parent budget, BOOKS-2011, of BK-GENERAL-2011 had at some point had its associated object codes (under Budget Info 2 tab) switched from “All” (the default) to all of the listed, individual object codes. I changed this back to “All”, but it has not corrected the errant behavior in the system.

    The pc_server log shows this:

    SERVICE : C0528
    MODULE : Acquisition Services
    DESCRIPTION: No Description Available
    PROGRAM : pc_acq_c0528

    Oracle error: io_z601_write
    ORA-01654: unable to extend index UTS50.Z601_ID2 by 512 in tablespace

    The "unable to extend" error occurs when the specific extent which Oracle is trying to add the file to becomes full. When the record resides in an extent which is not yet full you do not see the error.

    Adding 2-gigabyte datafiles to the following four tablespaces (all of which, as seen in util o/14/1, were getting low):


    corrected the problem.

    • Article last edited: 10/8/2013