- Article Type: General
- Product: Aleph
- Product Version: 16.02
We see this message in the ue_01 run_e_01 logs:
Oracle error: io_z07a_write
ORA-00001: unique constraint (xxx01.Z07A_ID) violated
What does this mean?
ue_01_z0102 sub process not running, z07a accumulating
The z07a table is the z0102 indexing request table. (Just as ue_01 indexes the doc numbers found in the z07 table, ue_01_z0102 does word and z0102 indexing for the doc numbers found in the z07a table.)
The z07a_id Oracle index is built from the z07a_rec_key -- which is the doc number. This message indicates that an attempt was made to write a z07a record for a doc number which was already in the z07a table. Since a doc number needs to be in the z07a table only once, this error may be ignored.
But if this error is occurring frequently (say, more than once every five minutes), it could indicate that z07a records are accumulating and not being processed as they should be.
The processes which read/update the z07a are the ue_01_word_index and the ue_01_z0102_index .
* check (with util c/1) to verify that these processes are running.
If they aren't, check the $data_scratch/run_e_01_word and run_e_01_z0102 logs to see why they stopped.
* Stop/restart ue_01.
If they are running, then do the following SQL repeatedly, about 10 times:
SQL> select count(*) from z07a;
If these repetitions show that the z07a never decreases -- that it always stays the same or increases --, that can indicate that the ue_01_z0102 or ue_01_word is not running properly.
If so, check the $data_scratch/run_e_01_word and run_e_01_z0102 logs for errors.
Category: Background processing (500)
Subject: Ue (500)
- Article last edited: 10/8/2013