Troubleshooting "ORA-00060 Deadlock Detected" Errors
(Doc ID 62365.1)
Last updated on NOVEMBER 06, 2020
Oracle Database - Enterprise Edition - Version 188.8.131.52 and later Oracle Database - Personal Edition - Version 184.108.40.206 and later Oracle Database Backup Service - Version N/A and later Oracle Database - Standard Edition - Version 220.127.116.11 and later Oracle Database Cloud Schema Service - Version N/A and later Information in this document applies to any platform.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!