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

Description:
We have a backlog of 750,000 z07's waiting to be processed in abc01. Why is this?

Resolution:
{The causes of large numbers of Z07s (indexing requests) being generated are described in KB 4093. In this case it seems that they have been generated by ue_08....}

We see that the current abc01 ue_08 created 4.9 million z07's (since March 28):

ABC01-ALEPH>>grep -c 'Update doc' run_e_08.3207366
4988229


This ue_08 activity was triggered by ue_11 (which updates the Z01_REC_KEY_4 to "-NEW-000000000")....

ABC50-ALEPH>>grep -c 'Update : d 00 ABC01 ABC10' run_e_11.3207366
458404


And we see large abc10 p_manage_37 logs in $alephe_scratch from early May:

ABC10-ALEPH>>ls -lrt abc10*
...
...
-rw-rw-r-- 1 aleph aleph 1011284 Apr 30 16:07 abc10_p_manage_37.00300
-rw-rw-r-- 1 aleph aleph 1181067 May 01 15:54 abc10_p_manage_37.00301
-rw-rw-r-- 1 aleph aleph 842162 May 04 13:06 abc10_p_manage_37.00302
-rw-rw-r-- 1 aleph aleph 846805 May 06 15:28 abc10_p_manage_37.00303
-rw-rw-r-- 1 aleph aleph 845989 May 08 15:41 abc10_p_manage_37.00304
-rw-rw-r-- 1 aleph aleph 1267856 May 11 15:08 abc10_p_manage_37.00305
-rw-rw-r-- 1 aleph aleph 1267274 May 12 17:22 abc10_p_manage_37.00306

These generated the abc10 updates (and z105 message records) which were processed by ue_11, which updated the abc01 z01's, which were processed by the abc01 ue_08 which generated the z07's.

If your authority records all have "UPD N" fields or if the updates you are performing via p_manage_37 are not making changes which need to be propagated to the abc01 bib records, then you can suppress the creation of abc01 z07's as follows:

(1) stop abc50 ue_11;
(2) run the abc10 p_manage_37;
(3) do abc10 util a/17/1 for the z105 (to empty/reinitialize the z105);
(4) start the abc50 ue_11


Despite the size of the queue, we see that all of the z07's have a sequence of "2009....", which means that they have a *lower* priority than new or updated GUI / oclc_server updates -- and, thus, are not interfering with current Cataloging activity.

• Article last edited: 10/8/2013