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

    Aleph high CPU (98%); ue_01; item update conflict

    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Problem Symptoms:
    1. High cpu load averages (as seen in "top"):

    2. At the same time, manage-50 ("Create Holdings and Item Records Using Bibliographic Data") running at this time hangs. The processes are still active, but the log has been un-written-to for an hour.

    3. Cataloger is unable to load records.

    4. The following messages in the Oracle alert log:
    Errors in file /exlibris/app/oracle/diag/rdbms/aleph20/aleph20/trace/aleph20_ora_6715.trc (incident=212248):
    ORA-00600: internal error code, arguments: [kksfbc-5wrong-kkscsflgs], [ <Jerry Specht > ]

    Incident details in: /exlibris/app/oracle/diag/rdbms/aleph20/aleph20/incident/incdir_212248/aleph20_ora_6715_i212248.trc
    Non critical error ORA-48913 caught while writing to trace file "/exlibris/app/oracle/diag/rdbms/aleph20/aleph20/incident/incdir_212248/aleph20_ora_6715_i212248.trc"
    Error message: ORA-48913: Writing into trace file failed, file size limit reached
    Writing to the above trace file is disabled for now on...
    Trace dumping is performing id=[cdmp_yyyymmdd...]

    Conflict between xxx01 manage-50 and xxx50 ue_01.

    Prevent ue_01 from running in xxx50 while manage-50 and certain other jobs are running in xxx01.

    Additional Information

    See KB 4130 {"Bib lib jobs which create/update items (p_manage_50, p_file_99, p_file_96) stall"}.

    In regard to ORA-48913 trace file error, see KB 16384-62977 ("Non critical error ORA-48913 caught while writing to trace file ... ")

    Category: System Management (500)

    Subject: Oracle (500)

    • Article last edited: 9/22/2014