Skip to main content
ExLibris

  • Subscribe by RSS
    • Primo
    Ex Libris Knowledge Center

    Pipe run fails during harvest stage

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Primo
    • Product Version: 4

    Problem Symptoms:
    ---------------------------
    ?· ? Pipe fails during 'nep' stage with status " 'stopped error - threshold exceeded', while processing job."
    ?· In BE log: "INFO [t-SplitRecords] [c-OriginalSourceRecordJDBCInsertUpdateService] - Existing entities found: {

    Cause:
    ----------
    Records are not split during the Harvest job due to existing records in the DB.
    Thus exceeding the initial threshold defined by the pipe (default 5%) and causing the job to fail.

    Resolution:
    Two options:
    -----------------
    1. ? Exclude from the ILS publish job the existing records in DB.
    2. Set the threshold value in the pipe's "Edit" menu to a higher Value to avoid pipe failing.

    Category: Publishing platform

    Subject: Harvesting

    • Article last edited: 10/8/2013
    //Feedback