In “Log Explorer”, Click on “Database Alert Logs”. Login to OMC and click on “Log Analytics”. If you have OMC configured and working, follow the below procedure to monitor, analyze and get alerted for a deadlock scenario. It works equally for your cloud or, on-premise environment. OMC is the next generation cloud-based offering from Oracle with integrated monitoring, management and analytics. To achieve this, I will detail 3 methods to get alerted when a deadlock occurs in the database. One obviously would not want too many deadlocks occurring in the database. While Oracle database is smart enough to handle a deadlock situation and perform the required action (statement rollback), often, it is necessary to be alerted if such a situation occurs. You can easily find the alert and trace file location by executing the below command: select di.value PATH, 'alert_' || i.instance_name || '.log' ALERT_LOG from v$diag_info di, v$instance i where di.name = 'Diag Trace' On the other hand, if a deadlock was encountered because of library cache, the trace file will have the following naming convention: _lmd0_.trc. The trace file which gets generated as a result of enqueue deadlock will have the following naming convention: _ora_.trc. The trace files which gets generated in each scenario, would have a difference in the naming convention. In Oracle RAC, for both enqueue and library cache deadlock events (ORA-00060 and ORA-4020), a related generic message (Global Enqueue Services Deadlock detected) is recorded in the database alert log. So, I will not go into the troubleshooting details, however, please check the “references” section of this article to quickly browse through them if that is the intent.
#Ora 00060 deadlock detected while waiting for resource how to
A deadlock occurs when two or, more sessions/ processes are waiting on each other to release the lock held by another sessions/ processes.
0 kommentar(er)
