- Article Type: General
- Product: Aleph
- Product Version: 20, 21, 22, 23
We get these messages in the pc_server log:
Oracle error: io_z65_write
ORA-00001: unique constraint (VIR01.Z65_ID) violated
The pc_server log shows one occurrence of the following message at the exact time that clear_vir01 was running :
The z65 is the pc_server session-id table. The z65 unique-constraint error occurs when the system tries to write a z65 record with the same key as an existing one. The pc_server is trying to assign the same session-id to this new session as that of an existing session, and the z65_id -- an Oracle index defined as UNIQUE -- is (correctly) preventing this. The vir01 UTIL-G-2 "session-id" counter is used to make the z65 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.
(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 z65 .
See KB 8192-1433 for a discussion of how to prevent this problem.
- Article last edited: 13-Apr-2016