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

Description:
A search query entered by one Web user appears on another user's screen; all Web users seem to be sharing the same, single session. The "Previous Searches" function shows searches by other users; not just yours (as it should).

The www_server log shows this:.
Oracle error: io_z63_write.
ORA-00001: unique constraint (VIR01.Z63_ID) violated.
WRITE ERROR X1BVFCNSMJBY7MAYX9HKVK4XG2275GLGGT1.

And "X1BVFCNSMJBY7MAYX9HKVK4XG2275GLGGT1" is the only session ID which appears anywhere in the www_server log.

Resolution:
This problem was due to the fact that the vir01 z52 (and the vir01 util g/2 session-id parameter) did not exist. To check this do:

dlib vir01
util g then "2"

You need to do util x/8 {"Clean Virtual Library (VIR01)"} with the "Cold" option. ("Hot" doesn't do anything with the z52.) It will ask you to shut down all the servers, queues, etc. If you are on version 18, you can do this with util w/5. In other versions, just stop the pc_server and www_server with util w/2.

If the preceding doesn't work for some reason, another method is to restore the z52.seq from the ./vir01/files (using p_file_03).

The *cause* of the missing z52 was almost certainly a failure in the most recent run of the clear_vir01job. Check the log for messages relating to the z52, such as: " SQL*Loader-908: Unable to lock table VIR01.Z52 due to ORACLE error 54 ".

If you do not see any z63_id errors and the z52 seems OK and if this is being reported by librarians doing OPAC testing, they may be using the same Web OPAC URL (passed from one to another). In this case, the solution is for them to stop doing this.