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

Description:
When you do keyword searches ("Find") the same record or records are repeated in the Brief List, regardless of what search you do. This happens with all libraries, including USM01. In the www_server or pc_server log you see messages like this:

Oracle error: io_z05_write
ORA-00001: unique constraint (VIR01.Z05_ID) violated

Oracle error: io_z110_write
ORA-00001: unique constraint (VIR01.Z110_ID) violated

Or, possibly:

Oracle error: io_sequence_next
ORA-02289: sequence does not exist

Resolution:
The "unique constraint" error indicates that you are trying to write a record with the same key as an already existing record. The z05 and z110 files are the result-set table, where search results are kept for redisplay. When the 6-digit key reaches 999999, the system starts over with a key of 000001, resulting in the "unique constraint" message. The solution is to run clear_vir01 to clean out the z05/z110.

We suggest adding the VIR01 "clear_vir01 VIR01", which clears not just the z05 and z110 but all of the vir01 tables, as a weekly or daily process to the job list.

**When you run clear_vir01 from the job_list, you need to make certain that the vir01 batch queue is running.** If the vir01 batch queue isn't running, then the vir01 util c/7 will show the accumulated clear_vir01 jobs waiting to run.

In one case, we had problems running clear_vir01 after the z05_rec_key 999999 was reached. See KB 8192-7896.

KB 5730 describes how the p_print_04 job can cause this problem.