The ORA-00060 error. As a DBA we can see that error message during daily database works.

As you know that error referred to as a “deadlock detected” error. It occurs in Oracle databases when two or more sessions are unable to obtain the necessary locks on a set of rows because each session is waiting for a lock to be released by the other. This situation creates a deadlock, where neither session can proceed. Here are some common details about this error:

• A deadlock occurs when two or more transactions are waiting for data locked by the other transaction to be released.
• The database administrator (DBA) or application developer needs to identify the deadlock and take appropriate action to resolve it.
  This may involve terminating one of the sessions involved in the deadlock or modifying the application code to avoid such deadlocks in the future.
• When this error happens, Oracle database can provides trace files that contain more detailed information about the deadlock, including the SQL statements involved, the objects locked, and the sessions participating in the deadlock.

To resolve the ORA-00060 error, you can take several steps, including:

• Rerunning one of the transactions after a short delay, allowing the other transaction to complete.
• Modifying the application code to access data in a consistent order, reducing the likelihood of deadlocks.
• Using Oracle’s deadlock detection and resolution mechanisms, such as setting appropriate isolation levels or using the DBMS_LOCK package to manage locks explicitly.

It’s important to note that preventing deadlocks often requires a combination of database design, application design, and careful monitoring and tuning of the database system.