Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    server failed to execute after 200 seconds" after p_manage_37 on HOL recs

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    After running p_manage_37 in the abc60 library, we are receiving the error message: "server failed to execute after 200 seconds" when trying to update holdings records.

    (Same has occurred with p_manage_50 in bib library and p_manage_21 and p_manage_18 in HOL library, etc.)

    Resolution:
    Workaround: This is like KB 16384-34161. We found that users needed to restart Aleph and Oracle to correct the problem with HOL record creation/update.
    Stopping the abc60 ue_01 before running jobs which update HOL or item records has prevented additional occurrences of the problem.

    Solution for p_manage_50: v20 rep_change 3673.

    Proposed solution for other jobs (not yet verified):

    (From Issue 42872) "This has been analyzed and discussed with DBA. The errors are due to a bug in Oracle. There is a solution and a patch that solves this (Oracle Server Patch Set 11.2.0.2 for version 21; or 11.1.0.7.2 for v20). See below....

    Modified 20-NOV-2010 Type PATCH Status PUBLISHED

    Bug 9066130 OERI [kksfbc-wrong-kkscsflgs] / spin with multiple children
    This note gives a brief overview bug 9066130.
    The content was last updated on: 18-NOV-2010
    Click here for details of each of the sections below.
    Affects:
    Product (Component) Oracle Server (Rdbms)
    Range of versions believed to be affected Versions BELOW 12.1
    Versions confirmed as being affected • 11.1.0.7

    Platforms affected Generic (all / most platforms affected)
    Fixed:
    This issue is fixed in • 12.1 (Future Release)
    • 11.2.0.2 (Server Patch Set)
    • 11.1.0.7.2 (Patch Set Update)
    • 10.2.0.5 (Server Patch Set)
    • 11.1.0.7 Patch 22 on Windows Platforms

    Symptoms: Related To:
    • Hang (Process Hang)
    • Internal Error May Occur (ORA-600)
    • ORA-600 [kksfbc-wrong-kkscsflgs]
    • ORA-600 [kksfbc-5wrong-kkscsflgs]
    • Waits for "cursor: mutex S" • (None Specified)


    Description
    ORA-600 [kksfbc-wrong-kkscsflgs] / ORA-600 [kksfbc-5wrong-kkscsflgs]
    can occur along with high CPU consumption under kksSearchChildList()
    and waits on event 'cursor: mutex S' for SQL with multiple versions.

    Workaround:
    Flushing the shared pool can help

    Note:

    Bug 9066130 for one-off requests for 11.1.0.7.x and older versions (per Bug 9439258)
    Bug 9067282 for one-off requests for 11.2.0.1.0 and later.

    Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice.
    References
    Bug:9066130 (This link will only work for PUBLISHED bugs)
    Note:245840.1 Information on the sections in this article
    ________________________________________
    ________________________________________

    Related
    ________________________________________
    Products
    ________________________________________
    • Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition

    • Article last edited: 10/8/2013