manage-21 and manage-37 generate large numbers of z07 records

• Article Type: General
• Product: Aleph
• Product Version: 20, 21, 22, 23

Description:
It seems that the p_manage_21 and p_manage_37 generate large numbers of z07 records -- which are processed by ue_01 and result in a lot of archiving activity.   Is this correct behavior?

Resolution:
Yes. Each record which is updated by p_manage_21 or p_manage_37 has a z07 (Indexing Request) record built for it.
This is because all record changes (batch or GUI) can affect indexes and, thus, need to have a z07 written for them.   However, if the change is one which doesn't need to result in any index change, then the Service could be run at a time when Cataloging updates are not occurring:

 * do s+ xxx01    select count(*) from z07;      if not zero, then run the file-03 Service in xxx01 to backup the z07's 

 * stop xxx01 ue_01 (util e/2)

 * run manage-21 or manage-37 

 * [optional, as a safety precaution]

      *  cd $data_root/files

      *   mv z07.seqaa z07.seqaa.save-pre    (if there were no z07's backed up in the first step, above, this mv step isn't necessary)

      *  run the file-03 Service to back up the xxx01 z07 table

 * (using util a/17/1)  drop/recreate the xxx01 z07 

 * restart the xxx01 ue_01 (util e/1)

But unless there are a lot of records being updated (more than, say, 500,000) and the ./arch disk space is low, this shouldn't be necessary.

• Article last edited: 11-Feb-2017