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

    p_file_20: "check_z308 routine failed. Can not ins/upd record...."

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description:
    We are having trouble loading a record for our SPC ADM. Here is an example from the reports log:

    <section-01>
    <form-date>07/31/2012</form-date>
    </section-01>
    <section-02>
    <line-number>1</line-number>
    <table-name>z303</table-name>
    <action>Insert</action>
    <match-id>99000190323</match-id>
    <user-name>Cesta,Jeffrey L.</user-name>
    <patron-id>SPCP516859</patron-id>
    <msg-code>5003</msg-code>
    <msg-desc>Unable to process record due to problems in other records.</msg-desc>
    </section-02>
    <line-number>1</line-number>
    <table-name>z305</table-name>
    <line-number>1</line-number>
    <table-name>z308</table-name>
    <action>Insert</action>
    <match-id>99000190323</match-id>
    <user-name>Cesta,Jeffrey L.</user-name>
    <patron-id>SPCP516859</patron-id>
    <msg-code>5021</msg-code>
    <msg-desc>check_z308 routine failed. Can not ins/upd record. cur-id SPCP516859.</msg-desc>
    </section-02>

    We have also been told that the Circulation Librarian cannot manually enter the patron with the ID 190323 because she gets a “duplicate error”. However, we cannot find any existence of the ID in the database.

    Can you please help explain what the problem is?

     

    Resolution:
    In the course of diagnosing this problem I did the following SQL:

    abc50@ALEPH20> select z308_rec_key, z308_id from z308 where z308_rec_key like '%190323%SPC50';
    **** Hit return to continue ****

    Z308_REC_KEY Z308_ID
    --------------------------- ------------
    01190323 SPC50

    This clearly indicates a defect: the z308_id should never be blank.

    It seems to me that this record should be deleted (with SQL).

    The following query shows that there are 390 other such cases:

    abc50@ALEPH20> select count(*) from z308 where z308_id like ' %';
    **** Hit return to continue ****

    COUNT(*)
    ----------
    390

    The following SQL shows the individual cases:

    SQL> select z308_rec_key from z308 where z308_id like ' %';

    I believe they are all type '01's (barcodes) -- and that they should all be deleted. 

    As noted in KB 16384-37074, v20 rep_change 3520 prevents records from being created with blank ID's. KB 16384-30387 may also be relevant.


    This is the (one) case where the z303_rec_key itself is blank:

    abc50@ALEPH20> select z303_name, z303_open_date from z303 where z303_rec_key like ' %';
    **** Hit return to continue ****

    Z303_NAME
    --------------------------------------------------------------------------------
    Z303_OPEN_DATE
    --------------
    PHC East
    20110201


    [From site:] I was able to load the record once the previous ID had been deleted.

     

     


    • Article last edited: 12-Mar-2016