Skip to Content
Author's profile photo Jeisson Leonel

Analysing Oracle Deadlocks – ORA-00060

Several times we face deadlocks error sand initially have no clue how to proceed, for that I’ve created a KBA number #1872040 that talks about such scenarios.

In fact there are two kinds of deadlocks, ORACLE and APPLICATION deadlocks, most of the times the locks are related to application and should be definitely treated by application area specifics. It’s very easy to identify if the deadlock is an oracle deadlock or not. See below images that show us the differences.

/wp-content/uploads/2013/10/application_296005.jpg

/wp-content/uploads/2013/10/oracle_296012.jpg

By exprience I believe that most of the deadlocks are generated by application level, in such cases we will need to consult application team specifics but if the deadlocks are from oracle the solution is still quite simple. By adjusting the INITRANS and MAXTRANS parameter of involved object, mentioned KBA detailed the steps you should take.

Hope you like this blog and any comments/suggestions are welcome!

Best regards,

Jeisson Leonel

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Krishna Chaitanya
      Krishna Chaitanya

      Hi Jeisson

      Thanks for sharing...very useful and informative.  🙂

      Regards,

      Krishna Chaitanya.

      Author's profile photo Eduardo Rezende
      Eduardo Rezende

      Nice blog Jeisson!

      Is there any default location to find the deadlock trace?

      Author's profile photo Former Member
      Former Member

      In short deadlocks indicate incorrect programming[X] or configuration of the DB instance[S]!