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

Description:
I modified tab17, adding catch all lines for each library for the first week of January. E.g.

BIRK ####0101 C
BIRK ####0102 C
BIRK ####0103 C
BIRK ####0104 C
BIRK ####0105 C
BIRK ####0106 C
BIRK ####0107 C
BIRK ####0108 C

and then ran p-cir-01. It had the following error:

CREATE UNIQUE INDEX ABC50.Z301_ID ON ABC50.Z301 (Z301_REC_KEY ASC)
*
ERROR at line 1:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

I put back the former tab17, and it rebuilt fine.

So, something wrong with my new tab17. I will go through it, but thought I would ask:
what type of error in the table would cause a duplicate indexing error?

I checked that there were no other lines covering those dates - from 0101 to 0108, so am not sure what is wrong. I will try to load the table again - in test!

Resolution:
[From site:]

I tested it on the test server and it was okay (having made no changes to the table). I then reloaded tab17 onto the production server, ran p-cir-01 and the index error did not re-occur.

[From Jerry:] The z301_id Oracle index is built on the z301_rec_key, which is the sublibrary code: each sublibrary has a single record with the due dates for that sublibrary.

Another site found that when p_cir_01 was run again the next day, it did not get the error.

• Article last edited: 10/8/2013