Interpretting a deadlock trace file

From: Schauss, Peter <peter.schauss_at_ngc.com>
Date: Fri, 27 Aug 2004 12:06:55 -0700
Message-ID: <A17F427EF83B5D4881E6B304F8781C5E47551E@xcgny001.northgrum.com>

I returned from vacation to find a trace file, the result of a deadlock detected in one of our applictions, in my udump directory.

It contained the text of one of the offending SQL statements, followed by what it called a "Deadlock graph"

Deadlock graph:

                       ---------Blocker(s)--------  ---------Waiter(s)---------
Resource Name          process session holds waits  process session holds waits
TX-0003002a-0000a0c8        23      70     X             17     119           X
TX-00020028-0000a1b5        17     119     X             23      70           X
session 70: DID 0001-0017-00000002      session 119: DID 0001-0011-00000002
session 119: DID 0001-0011-00000002     session 70: DID 0001-0017-00000002

Looking at this it seems that session 70 was holding a resource identified by TX-0003002a-0000a0c8 and waiting on TX-00020028-0000a1b5 and that session 119 was doing the oposite. How do I translate these values to actual database objects (i.e. table names, indexes, ...)?

Thanks,
Peter Schauss

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

Received on Fri Aug 27 2004 - 15:37:08 CDT