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

    ORA-00001: unique constraint (XXX50.Z305_ID) violated with PLIF (p_file_20)

    • Article Type: General
    • Product: Aleph

    Problem Symptoms:
    Loading new patrons via PLIF (p_file_20) gives this error in logfile:

    Oracle error: io_z305_write
    ORA-00001: unique constraint (XXX50.Z305_ID) violated

    The PLIF input file used by customer first includes "real" sub-library record for Z305 (sub-library "ABC") and then XXX50-record for z305.

    In Aleph when a "real" sub-library record is created, always the ADM-record (XXX50) is created automatically at the same time with the same values. This is hardcoded and can not be configured. This means that at the stage PLIF is processing the XXX50-record from input file, it already exists (because it was created while handling the ABC-record) and an Oracle error is produced.

    To get rid off this message there are two options:

    a) Remove XXX50-records from input file as PLIF is creating them automatically while handling the other z305. So it is not needed to include them explicitely.

    b) Change the order and move in the XXX50-record prior to the ABC-record (this might be useful in case for any reason you want to create XXX50-record with other values than ABC-record).

    • Article last edited: 12/17/2013