Oracle error: update_cursor z305; partition of such index is in unus

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

Description:
One of our instances cannot access their patron file this morning. I checked the pc_server log and this Oracle error appears numerous times:

Oracle error: update_cursor z305
ORA-01502: index 'ABC50.Z305_ID' or partition of such index is in unus [unusable state]

I know this error is written to the log for other tables (e.g. z08) with no functional error, but in this case, this error corresponds to my attempts to access the patron file in ABC50.

Our Aleph programmer tried rebuilding the index using util_a_17_03 and got the following:

ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

He is trying to delete the duplicate keys (there's a bunch of them) and is going to rebuild the index when finished.

Resolution:
The util a/17/18 utility can locate duplicate records, delete them, and build the relevant Oracle index as "Unique".

util a/17/14 shows that the cfu50 z305_id Oracle index is now present and valid.

$LOGDIR/pc_server_6570.log and pc_server_6573.log show that no ORA-01502 errors have occurred in the past hour. So it seems that it's fixed.

I see (in the 6573 log) that this problem was present at 6:44 this morning. Was there a batch update of patron records last night which might have caused this? I think of the p_file_20 PLIF load, but I don't see that....

• Article last edited: 10/8/2013