Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Aleph to Primo Publishing: Primo indexing running out of Oracle TEMP space

    Aleph to Primo Publishing: Primo indexing running out of Oracle TEMP space

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • 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
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Aleph to Alma migration: Items with temporary locations
      • Aleph Update IGeLU 2012.pdf document mention new service p-acq-33
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 20
      2. contype:kba
      3. Interoperability (500)
      4. Primo
      5. Prod:Aleph
      6. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved