Oracle FAQ

Your Portal to the Oracle Knowledge Grid

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US

Home -> Community -> Usenet -> c.d.o.server -> Re: How, specifically, can I find out the cause of deadlock from a trace file?

Re: How, specifically, can I find out the cause of deadlock from a trace file?

From: NetComrade <netcomradeNSPAM_at_bookexchange.net>
Date: Tue, 16 May 2006 12:10:53 -0400
Message-ID: <uhtj629p52pkgca1ce7c1k33ptt5mbvmnd@4ax.com>

On 16 May 2006 08:35:58 -0700, "theRat" <john_hilgedick_at_yahoo.com> wrote:

>Session 13: obj - rowid = 00008DB5 - AAAI21AANAAAF+SAAS
> (dictionary objn - 36277, file - 13, block - 24466, slot - 18)

metalink has a ton of documents on deadlocks.

You should be able to figure out what object the contention is for from this

select segment_name, partition_name from dba_extents where file_id=&1 and &2 between block_id and block_id+blocks; .......
We run Oracle 9iR2,10gR1/2 on RH4/RH3
remove NSPAM to email Received on Tue May 16 2006 - 11:10:53 CDT

This message: [ Message body ]
Next message: Chuck: "Re: Veritas Cluster, 10g EM agent configuration"
Previous message: hypermodest_at_gmail.com: "cheapest Oracle product to get metalink access?"
In reply to: theRat: "How, specifically, can I find out the cause of deadlock from a trace file?"
Next in thread: Chuck: "Re: How, specifically, can I find out the cause of deadlock from a trace file?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US