p_manage_01: unique constraint (ABC01.Z98_ID) violated

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

Description:
We did a restart of p_manage_01_e on our 10-million-bib database (as described in "How To Run Index Jobs", Section 9). The 'e' section finished and p_manage_01_e.cycles shows '+' for all cycles, but it looks like there were some problems:

z98.bad is not empty.

The z98_dmp_ora.log files show a lot of unique constraint errors like:

Record 51: Rejected - Error on table UXU01.Z98.
ORA-00001: unique constraint (ABC01.Z98_ID) violated

followed by

MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.

Table ABC01.Z98:
0 Rows successfully loaded.
51 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.

Resolution:
The first step in the Restart of p_manage_01_e procedure is:

• Drop/recreate the z98 table (using util a/17/1).

The above symptoms can be the result of failing to do this. A p_manage_01_e run preceded by the drop/recreate was successful.

Another cause could be unlocking the library and having the abc01 ue_01 running while the p_manage_01_e is running. You can't do this.

• Article last edited: 10/8/2013