My Oracle Support Banner

Troubleshooting "ORA-00060 Deadlock Detected" Errors (Doc ID 62365.1)

Last updated on NOVEMBER 06, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 7.0.16.0 and later
Oracle Database - Personal Edition - Version 7.1.4.0 and later
Oracle Database Backup Service - Version N/A and later
Oracle Database - Standard Edition - Version 7.0.16.0 and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.

Purpose

This document helps diagnose and troubleshoot ORA-60 "deadlock detected while waiting for resource" errors.

NOTE: Deadlock errors are usually not the underlying root cause of a problem, rather they are more likely to be an indicator of another issue in the application or elsewhere. Once the resultant trace file has been examined (as shown later in this document) to determine the objects involved, it is then worth thinking about what could be causing such a deadlock - for example a batch program being run more that once by mistake or in the wrong order, or by not following programming standards in an application.

Identification and Resolution of the underlying issue then makes the error redundant.

 

Scope and Application

This article is intended for Oracle Support Analysts , Oracle Consultants, Database Administrators and Application Developers.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
 Scope and Application
Troubleshooting Steps
 What is a Deadlock?
 Example of Deadlock
 Diagnostic information produced by an ORA-60
 What does the trace information mean ?
 Avoiding Deadlock
 Different Lock Types and Modes
 TM locks - which object ?
 How to obtain Additional Information
 Self Deadlock Issue
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.