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

    Can't log into Web, "unique constraint (VIR01.Z63_ID) violated" *MASTER RECORD*

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

    Description:
    Some users can't log onto the Web. The www_server log shows one occurrance of the following message at the exact time that clear_vir01 was running :

    Oracle error: io_z63_write.
    ORA-00001: unique constraint (VIR01.Z63_ID) violated.

    Some users are able to get into the Web, but they are getting results from other users' sessions.

    What should be done?

    Resolution:
    The z63 is the Web OPAC session-id table. The z63 unique-constraint error occurs when the system tries to write a z63 record with the same key as an existing one.
    The vir01 UTIL-G-2 "session-id" counter is used to make the z63 session-id unique.

    In this case, UTIL-G-2 was blank. This indicates that the vir01 z52 table is missing. (Probably because the z52 step of the previous night's clear_vir01 failed for some reason.)

    Check the vir01/$data_files to see if there's a z52.init file. (This file is used by clear_vir01 to initialize the z52.) If not and if there *is* a z52.seq file, then copy the z52.seq to z52.init.

    Then either:

    (1) rerun clear_vir01 or

    (2) do p_file_04 to load the vir01 z52 table:

    csh -f $aleph_proc/p_file_04 VIR01,z52,replace > & $alephe_scratch/p_file_04_vir01_z52.log &

    followed by UTIL-A-17-1 for the vir01 z63 .

    See KB 8192-1433 for a discussion of how to prevent this problem.

    Additional Information

    web, clear_vir01, z63, unique constraint, index, faq


    • Article last edited: 10/8/2013
    • Was this article helpful?
    //Feedback