Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Publishing extract fails with Java heap space error

    • Article Type: General
    • Product: Voyager
    • Product Version: 8.2.1

    Problem Symptoms

    •  After Voyager upgrade, running Publishing extract (Pprimoexp.pub) fails or hangs
    •  Error prints to screen or appears in primo.export.[datestamp].log: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
    •  Files may not finish being packaged (.tar.gz) in /m1/voyager/xxxdb/primo/Publishing/bundled/

    Cause

    Upgrade included a headings regen; when publishing extract attempts to process all records with headings changes using a changed since date prior to upgrade, it runs out of Java memory.

    Resolution

    1. Edit /m1/voyager/xxxdb/ini/PrimoExp-Publishing.ini
    2. Modify the HeadingChanges option to ensure headings changes are NOT processed:

    # HeadingChanges determines whether to export bibliographic records

    # whose cross-references have changed

    # -H Y|N overrides this parameter on the command line

    HeadingChanges=N

    1. Save PrimoExp-Publishing.ini
    2. Run Publishing extract again, using same ChangedSince date
    3. After extract is complete, switch HeadingChanges setting back to "Y" to process any headings changes moving forward.

    • Article last edited: 8-Oct-2013
    //doorbell.io feedback widged