Aleph to Primo Publishing: Primo indexing running out of Oracle TEMP space
- Article Type: General
- Product: Aleph
- Product Version: 20
Problem Symptoms:
* Records recently created/updated in Aleph can not be found in Primo.
* These records have z00p records with AVA fields with <subfield "e" available> in xxx50. They were processed by publish-06 ("Create a tar file for Aleph published records") and are included in the tar file it produced.
Cause:
In Primo, the record was created (per the PNX Viewer). However, the Primo Indexing process has not completed because Primo has been running out of Oracle TEMP space.
Resolution:
* Increasing Oracle TEMP space in Primo allowed the currently running Indexing Process to complete successfully.
* The "missing" records are now searchable in Primo.
Additional Information
Specific case at customer site:
Records recently created/updated in Aleph can not be found in Primo. For example:
002288583 ("Das Klavierwerk Vol. 1 [sound recording] Fanny Hensel-Mendelssohn.") and
002288576 ("The price of inequality how today's divided society endangers our future")
These records have z00p records with AVA fields with <subfield "e" available> in xxx50. They were processed by publish-06 on Sept. 18 and are included in the aleph.PRIMO-FULL.20120918.073010.1.tar.gz file it produced on Sept. 18:
> ls *002288583*
ABC01.002288583.PRIMO-FULL.xml
> ls *002288576*
ABC01.002288576.PRIMO-FULL.xml
These *should* have been processed by the Primo pipe on Sept. 18, but we don't see the records in Primo.
**** In Primo, the record was created (per the PNX Viewer) on 09/18/2012 at 09:36. However, the Primo Indexing process has not completed since the run that started at 8:30a that same day. Primo has been running out of Oracle TEMP space.
Category: Interoperability (500)
Subject: Primo
- Article last edited: 10/8/2013