Skip to main content
ExLibris

  • Subscribe by RSS
    • Primo
    Ex Libris Knowledge Center

    Pipe Failed with Error: deadlock detected while waiting for resource

    1. Last updated
      00:22, 9 Dec 2015
    2. Save as PDF
    • Article Type: General
    • Product: Primo
    • Product Version: 4

    Problem Symptoms:
    Our pipe has just failed with error:
    The pipe <PIPE NAME>, that started at <DATESTAMP> failed at <DATESTAMP> in stage 'nep' with status 'stopped error', while processing job 2012.06.27-17.30.00-175023390 The error message is:
    java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource

    Cause:


    Resolution:
    You can simply re-execute the Pipe and it should complete.

    This can occur because another process is running (deadlock in the DB).
    There is an open development issue regarding a problem in the Pipe queue mechanism: in M_P_WORK (pipe statuses) and R_T_PIPE_CONFIGURATION tables.

    If this problem continues, open an SI or MeToo this SKB article.
    Note that there should be more information in the $ORACLE_ALERT_LOG file, for example:
    ?’?‚¬?¿½ORA-00060: Deadlock detected. More info in file /exlibris/app/oracle/diag/rdbms/prm4/prm4/trace/prm4_ora_19334.trc.?’?‚¬?¿½

    Category: Publishing platform

    Subject: Harvesting

    • Article last edited: 10/8/2013