p_manage_01: p_manage_01_d: "Index failure after load: Z95_ID=UNUSABLEn"
- Article Type: General
- Product: Aleph
- Product Version: 18.01
Description
The $data_scratch/.../p_manage_01_d1.log has this at the end:
FAILURE Thu Oct 15 08:07:44 PDT 2009 ==================
step 4
Cycle: 1
Index failure after load: Z95_ID=UNUSABLE\n
Job Suspended !!!
Resolution
util a/17/14 for z95 showed the z95_id as "UNUSABLE".
We did util a/17/4 to drop the z95_id and util a/17/2 to recreate it, but the latter got the
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
message.
Duplicate z95's could be caused by unlocking the library and letting ue_01 run while p_manage_01 is running, but that was not the case here.
We instructed the site to try running the job again, with exactly the same parameters as before. This second effort ran OK; Word indexes are available and correct.
-
Additional Information
The problem can be caused if the process ue_01 isn't stopped correctly.
-
-
In this case, you should follow the instructions below on the library xxx01:
-
2. util e/2 to stop process ue_01
3. util c/1 to check that the process ue_01 don't run.
If it is the case, killed the ue processes I found running there (manage-01 *should* do this but it seemed it wasn't for some reason).4. resubmitted the bib01 manage_01
-
- Article last edited: 29-Aug-2016