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

    Oracle deadlock errors

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

    Description:
    Yesterday we noticed in the Oracle alert log an ORA-000060 deadlock error. This is not the first time we had it. Further investigation found that the error was reported in the abc01 run_e_01.7965.

    The alert error was:
    Mon Jun 5 15:57:15 2006
    ORA-000060: Deadlock detected. More info in file /oradata/admin/cuny16/udump/...16_ora_3283.trc.
    Mon Jun 5 15:57:19 2006
    ORA-000060: Deadlock detected. More info in file /oradata/admin/cuny16/udump/...16_ora_15478.trc.
    Mon Jun 5 15:57:22 2006
    ORA-000060: Deadlock detected. More info in file /oradata/admin/cuny16/udump/...16_ora_3283.trc.
    Mon Jun 5 16:04:05 2006

    run_e_01 alert had:
    HANDLING DOC NO. - ABC01.004794046 15:57:11

    Oracle error: io_z13_update
    ORA-00060: deadlock detected while waiting for resource

    Can anything be done about this error?

    Resolution:
    Our second line support group has examined the pc_server log, ue_01 log, and udump trace files. They have determined that this deadlock error message is occurring because the CAT update program (pc_cat_c0203) and the background indexing daemon (ue_01) are both trying to update the indexes for the same record at the same time. They also found that this same condition can sometimes result in this error in the pc_server log:
    Oracle error: io_z120_write
    ORA-00001: unique constraint (CUN01.Z120_ID) violated

    The record and its corresponding indexes are, nevertheless, all being updated correctly, so these messages can be ignored.

    • Article last edited: 10/8/2013