- Article Type: General
- Product: Aleph
- Product Version: 20
"Create Tar File for ALEPH Published Records (publish-06)" runs properly but creates no tar file in which the published records are transferred to e.g. Primo. At the end of the log file error message "no tar file created for the set:nnn" is reported. (This message is seen in the $data_scratch log file, but not in the $alephe_scratch log file.)
1. tab_publish_timestamp file or
2. ue_21 daemon not running
The following SQL will show if there are z07p (publishing requests) waiting to be processed by ue_21:
SQL> select count(*) from z07p;
1) Table /exlibris/aleph/ann_n/aleph/tab/tab_publish_timestamp which holds the next publish date is missing or has a wrong date.
The table has one line which should look like this:
<where PRIMO-FULL?€¦ is the publishing set and "nn" is the day of the month you want to use as the last date>
2) Daemon ue_21 was not running for some time. Z07P records were produced but, the z00p was not updated. Consequently p_publish_06 had no records to work on.
Restart ue_21 in BIB library.
If, under version 22, the ue_21 log has an ?€œexpand_doc_bib_avail.gnt?€? error, this is due to a bug. See Article 45277 [ue_21 crashes with "Execution error ... Attempt to access item beyond bounds of memory"] for the fix.
Category: Publishing Services - ALEPH
Subject: ALEPH - 500
- Article last edited: 2/5/2015