• Article Type: General
• Product: Aleph
• Product Version: 20, 21, 22, 23

Description:
The manage-01 (p_manage_01) on the stage server ran with the errors below.
What is the significance of those errors? How should I proceed?
Job-number: 8148
Job-name : Rebuild Word Index (manage-01)
Parameters: ABC10,1,000000000,999999999,,06,
Start At : 01/15/2011 09:30 AM
End At : 01/15/2011 06:21 PM
Status :
Log File : /exlibris/aleph/u20_1/alephe/scratch/abc10_p_manage_01.00113
Job Type : INDEX
User : SMITH

Job Errors
--------------------------
Error found in log file: Sat Jan 15 18:16:53 EST 2011 Error : Only 2 indexes out of 3 for table z97 were created
Error found in log file: Sat Jan 15 18:21:06 EST 2011 Error : Only 0 indexes out of 1 for table z98 were created

Resolution:
We see the following errors in the abc10 $data_scratch/create_ora_tables_z97_id3.log:

aleph_admin@ALEPH20> 18:15:56 aleph_admin@ALEPH20> CREATE UNIQUE INDEX ABC10.Z97_ID3 ON ABC10.Z97 (Z97_REC_NUMBER_2 ASC)
*
ERROR at line 1:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

and the following in the abc10 $data_scratch/create_ora_tables_z98_id.log

aleph_admin@ALEPH20> 18:16:56 aleph_admin@ALEPH20> CREATE UNIQUE INDEX ABC10.Z98_ID ON ABC10.Z98 (Z98_REC_KEY ASC)
*
ERROR at line 1:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found


Article "Cannot CREATE UNIQUE INDEX; duplicate keys found; using util a/17/18 **HOW TO**" (KB 8192-424) describes this issue generally and article "p_manage_01: z98_id: cannot CREATE UNIQUE INDEX; duplicate keys found" (KB 16384-31153) addresses the z98_id specifically.

In view of the fact that util 17/18 did not give a satisfactory result in the case of the KB 16384-31153 z98_id, I suggest that you:
1. Run p_manage_01 for abc10 exactly as you did on Saturday.
2. If you get the same duplicate keys errors, then do util a/17/18 for the problem indexes (z97_id3 and z98_id), as described in KB 8192-424.
[From site:] The p_manage_01 was run again for abc10 exactly as on Saturday, and completed without errors. No obvious reason why it worked this time.
There was another case where a second run, with the same parameters, worked.

If the problem occurs with a library where manage-01 is being run for the first time, see the Article "p_manage_01 in xxx60: Z97_ID3; cannot CREATE UNIQUE INDEX; duplicate keys found".

• Article last edited: 22-Mar-2016