ue_21 stops processing records; z07p count growing; z07p_rec_key 000000000
- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Description:
ue_21 had been processing z07p records successfully before but seems to have stopped about a week ago. The count of z07p records keeps going up.
The ue_21 process continues to appear in util c/1 but is not doing anything. Stopping/restarting the process does not help.
The $data_scratch/run_e_21 log looks like this:
START UE-21 A 21:52:43
The Active hours of ue_21 are:
Hour Active=*
00 *
01 *
...
...
22 *
23 *
Load: /exlibris/aleph/u20_1/alephe/tab/tab_library_group
Load: /exlibris/aleph/u20_1/alephe/tab/tab_system_status
Load: /exlibris/aleph/u20_1/alephe/tab/tab100
Load: /exlibris/aleph/u20_1/abc01/tab/tab100
There are *no* "HANDLING DOC NO." lines (--which there should be).
Resolution:
Is ue_21 running in a bib, authority, or course library? It should be running in one of these only (-- not the usr_library).
An analysis of ue_21_a.cbl showed that it does not expect any z07p record with z07p_rec_key "000000000" (which is an illegal key). I found that, though there is no z00 record with z00_doc_number 000000000, a z07p with the key "000000000" was written on August 30, around 12 noon:
SQL> select * from z07p where Z07P_REC_KEY = '000000000';
Z07P_REC_ Z07P_TIMESTAMP
--------- ---------------
000000000 201008301211314
After I deleted this z07p with z07p_rec_key "000000000", ue_21 immediately started processing normally.
Note: v21 rep_change 2086 prevents z07p records from being created with keys of "000000000".
- Article last edited: 12-Mar-2016