Problem:
-------------
ORA-00060: deadlock detected while waiting for resource
Solution:
----------
Go to database trace folder /../../../trace/
cat alert_DBNAME.log |grep -i deadlock
ORA-00060: Deadlock detected. See Note at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /../../../../trace/SID_ora_XXX.trc
open one of the trace file and see what causing issues
see the "[Transaction Deadlock]" section to see if it is really an ORACLE errors
see the "Deadlock graph: " for any deadlocks
check for the Information , DML statements for the current (blocker) session and OTHER waiting sessions..
DBA do not have to do anything unless they are oracle errors, most of the cases i see , these are application issues. Design application and/or tune DMLs are the solutions.
A deadlock occurs when 2 sessions block each other by attempting to update a row, which is already updated by another session but has not been yet committed or rolled back. There can be more than 2 sessions involved, but the main idea is the same.
ReplyDeletehttp://dbpilot.net/2018/01/15/ora-00060-deadlock-detected-while-waiting-for-resource/
...