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

    p_manage_33: update_cursor1 z11, io_z13_write, etc., errors

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

    Description:
    We loaded bibs, items, holdings using the wrong loaders and config files (manage-18 and manage-50) on our production server for one of our libraries (ABC50) and want to delete the records and reload them using the correct loader (file-99) and config files.

    There were 194 records loaded for ABC50. You can see numerous errors in the p_manage_50 log file because the wrong configuration files were used for these records, but at the end, it shows that 194 bib, adm, holdings, item records were created.

    We were going to use manage-33 to delete these records and extracted one record from the manage-18 log file to use to test this on our production server before we deleted all of the records that were loaded. The p_manage_33 log has numerous ORA errors that I have never seen before. Can you explain why we got these errors?

    Oracle error: update_cursor1 z11
    ORA-00942: table or view does not exist

    Load: /exlibris/aleph/u19_1/sys50/tab/tab11_ind
    Load: /exlibris/aleph/u19_1/sys50/tab/tab_z103

    Oracle error: io_z13_write
    ORA-00947: not enough values

    Load: /exlibris/aleph/u19_1/sys50/tab/tab_z105

    Oracle error: update_cursor z07
    ORA-00942: table or view does not exist

    Oracle error: io_z07_write
    ORA-00942: table or view does not exist

    WARNING: cannot write Z07 for SYS50-007059290. See above io_z07_write message.

    Oracle error: delete_loan_from_adm
    ORA-00942: table or view does not exist

    loan : 11

    Oracle error: delete_loan_his_from_adm
    ORA-00942: table or view does not exist

    loan_his : 11

    <etc.>

    Resolution:
    Looking at the sys01_p_manage_33, I see that the messages relate to sys50.

    sys50 is your $usr_library. ADM records were created in SYS50. When you ran p_manage_33 it found these sys50 links, wanted to delete these ADM records, and did standard checking for entries in index tables (z11, z13, z07, etc.) needing to be deleted. Since the z11 and z13 don't exist in sys50 (being just the usr_library) it didn't find them.

    The z13 does exist in sys50, but it is in the old format (with the Z13_USER_DEFINED fields) rather than the new (with no Z13_USER_DEFINED fields in the Z13 itself ... just the Z13U).

    That's why you get:

    Oracle error: io_z13_write
    ORA-00947: not enough values

    It was never converted, but since it's extraneous, you should just remove it from the sys50 file list and drop it.

    There are 69 (DEL Y) sys50 ADM doc records:

    sys50@ALEPH1> select count(*) from z00;
    **** Hit return to continue ****

    COUNT(*)
    ----------
    69

    You could physically remove these (with SQL) but they are doing no harm.

    I think everything is fine. It seems you understand the root problem ("wrong configuration files were used for these records"), so, as long as you avoid that in the future, you shouldn't see this again.


    • Article last edited: 10/8/2013