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

Description:
We applied the February service pack this morning and the z07 table seems to be filling up. Is this something triggered by the service pack or is somethings else going on.

It appears the records came from ABC50 library where ue_01 hadn't been running for a couple months. Is it safe to just truncate the remaining records in the ABC50.z07 tables?

Resolution:
I doubt this is caused by the Service Pack -- except perhaps indirectly -- as you suggest, the start of ABC50....

The following SQL shows where the abc01 z07's have come from:

abc01@ALEPH20P> select substr (z07_history, 1,5), count(*) from z07 group by substr (z07_history, 1,5);
**** Hit return to continue ****

SUBSTR(Z07_HIST COUNT(*)
--------------- ----------
ABC01 341
ABC60 19
ABC50 53586


Please use KB 8192-2743 to analyze the ABC50 situation.

The following in the ABC50 $data_scratch shows that the ABC50 ue_01 processed 71,702 z07's (before you stopped it):

> grep -c HANDLING run_e_01.19604
71702

Since you do not have indexes in ABC50, it seems to me that you can do util a/17/1 (in ABC50) to drop/create the ABC50 z07.

Aside from this, I would leave the abc01 ue_01 running. The current cataloging will be given priority.

To prevent this situation in the future, I suggest that you comment out the following line in aleph_start.private:

setenv WORD_STARTUP_LIBS "$WORD_STARTUP_LIBS ABC50"

• Article last edited: 10/8/2013