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

    unique constraint (xxx50.z34_ID )"

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

    Description:
    Oracle errors when you search in the Web OPAC or the GUI search:
    Oracle error: io_z34_write
    ORA-00001: unique constraint (xxx50.Z34_ID) violated
    What does this mean?

    Resolution:
    The "unique constraint" error indicates that you are trying to write a record with the same key as an already existing record. The z34 is the IP Statistics table. There is only one z34 table per server (that of the pw_library). {The pw_library is specified in aleph_start (setenv pw_library).}

    The system uses the last-z34-sequence number in the util g/2 of the pw_library to decide what key to assign next. When a key of 9999999 is reached, the system starts over with a key of 0000001. Thus, the unique constraint can result from either the z34 being filled up {in which case this SQL in the $pw_library gives you a result of 10000000:
    "select count(*) from z34"} or from the last-z34-sequence being mis-set.

    In the former case, you should run UTIL A 13 ("Drop statistics table") to clean out the z34. (We suggest adding the UTIL A 13 to the job daemon as a weekly routine.)

    In the latter, you would re-set the last-z34-sequence to a correct value.

    A Z34 record is generated automatically by the system if the create_statistics flag in ./alephe_root/pc_server_defaults and www_server.conf is set to "Y". The system does not require this. As described in Article 000004879 ("When are z34's written? z34 vs. z69"), for the Web OPAC, the z34 has been superceded by the z69. We suggest that you change its value to"N" (-- and remove the util_a_13_b line from the job_list). You should also do: SQL> drop table z34;

    Additional Information

    Oracle error, z34


    • Article last edited: 2/13/2015