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

    p_file_20: "key conflict" after moving ssn from z308 type 00 to type 03

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    We have moved the ssn from the z308 type 00 to the type 03.

    We are trying to load an older PLIF file to the test system. Its giving us an error, telling us it can not update the record. However in our Train Enviroment it will update and run perfectly.

    Is this because the fields are now changed?

    The p_file_20 log has these messages:

    Load: /tmp/utf_files/aleph/aleph/u18_1/\abc50/tab/tab_bor_id.eng
    Error (b_file_20_chk_edit_record) : Duplicates in Z308 Record 000001
    Number of Errors = 01
    Info: Empty table /tmp/utf_files/aleph/aleph/u18_1/alephe/error_eng/check_z308
    Info: Empty table /tmp/utf_files/aleph/aleph/u18_1/alephe/error_eng/global
    Load: /tmp/utf_files/aleph/aleph/a18_1/aleph/error_eng/check_z308
    Error 0400 : key conflict

    Load: /tmp/utf_files/aleph/aleph/u18_1/abc50/tab/tab31
    Load: /tmp/utf_files/aleph/aleph/u18_1/alephe/tab/tab_sub_library.eng
    System is adding z308 type 01.

    Resolution:
    The ssn has been moved from the z308 type 00 to the z308 type 03.

    Bytes# 2 and 3 in each PLIF record are the MATCH-ID-TYPE. Looking at simspart.plif.04262010 I see that it has "00" as the MATCH-ID-TYPE.

    This needs to be changed to 03.

    • Article last edited: 10/8/2013