Re: Deadlock Detection

Tom, You should have 2 of these traces, one for each process involved. In this case, the processes are 22, 18 and 24, 27. If you run them through tkprof, they will be more readable, but the information is there. You need to look up the table, based on the resource id that was given under th

Re: Deadlock Detection

Hi         Your deadlock problem seems to be related to distributed transactions since your processes are holding and waiting for DX type locks. DX enqueues are taken for distributed queries. Do you have queries accessing the remote tables over the database links ?         As far as I know, even

Re: Deadlock Detection

i think i've been there and done that(Kevin T u know what i'm talking about),   Question, do you have bitmap indexes on the tables being updated?  if so, then thats your culprit.    joe   >>> [EMAIL PROTECTED] 06/22/01 09:35AM >>>All,My current application (still under development) is exper

Re: Deadlock Detection

Is it 8.1.6.3?>?  It had lots of deadlock problems.>>> [EMAIL PROTECTED] 6/22/01 9:35:56 AM >>>All,My current application (still under development) is experiencing Oracledeadlock problems.  The applications people are performing stress testingwhere the application is being repeatedly called

RE: Deadlock Detection

The "DX" resource is a new one on memaybe i just haven't had coffee yetare you, by chance, in a distributed database environment? are links involved? -Original Message- Sent: Friday, June 22, 2001 9:36 AM To: Multiple recipients of list ORACLE-L All, My current application (sti

Re: Deadlock Detection

Tom, The information you need should be in the trace file, but it's not in the excerpt you've listed, but the true problem is listed: > Rows waited on: > Session 27: no row "No row" indicates that the deadlock is due to a lack of available ITL slots in the datablock. Unfortunately resolving th

RE: Deadlock Detection

wow. great post. -Original Message- Sent: Friday, June 22, 2001 11:50 AM To: Multiple recipients of list ORACLE-L Tom, The information you need should be in the trace file, but it's not in the excerpt you've listed, but the true problem is listed: > Rows waited on: > Session 27: no r

Re: Deadlock Detection

ecipients of list ORACLE-L <[EMAIL PROTECTED]>         cc:                 Subject:        Re: Deadlock Detection Tom, The information you need should be in the trace file, but it's not in the excerpt you've listed, but the true problem is listed: > Rows waited on: >

RE: Deadlock Detection

Anita & Riyaj,   Thanks for the replies.  My email server "went away" for awhile, so I am just getting your replies now.   Anita, I am able to modify INITRANS for the tables (I tried this on a test table), and I will try this.  Right now, we are performing other stress tests to narrow down

RE: Deadlock Detection

ecipients of list ORACLE-L <[EMAIL PROTECTED]>         cc:                 Subject:        RE: Deadlock Detection Anita & Riyaj,   Thanks for the replies.  My email server "went away" for awhile, so I am just getting your replies now.   Anita, I am able to modify INITRANS for

Re: Deadlock Detection

se respond to ORACLE-L > > > To: Multiple recipients of list ORACLE-L > <[EMAIL PROTECTED]> > cc: > Subject:Re: Deadlock Detection > > > Tom, > > The information you need should be in the trace > file, > but it'

RE: Deadlock Detection

Anita, It must be a lack of sleep thing. :) Paul -Original Message- Sent: Friday, June 22, 2001 7:46 PM To: Multiple recipients of list ORACLE-L Riyaj, Doh! My bad. I completely missed the DX. You are absolutely correct that what I wrote is applicable only to TX locks. Thanks for

RE: Deadlock Detection

Did you check bug 1328999 if it applicable in your case. Regards, Waleed -Original Message- Sent: Friday, June 22, 2001 9:36 AM To: Multiple recipients of list ORACLE-L All, My current application (still under development) is experiencing Oracle deadlock problems. The applications

Re: Deadlock Detection

Try to look at the latch waits and session waits events. "Mercadante, Thomas F"

RE: Deadlock Detection - Resolved

-Original Message-From: Mercadante, Thomas F [mailto:[EMAIL PROTECTED]]Sent: Friday, June 22, 2001 3:48 PMTo: Multiple recipients of list ORACLE-LSubject: RE: Deadlock Detection Anita & Riyaj,   Thanks for the replies.  My email server "went away" for awhile, so I a

RE: Deadlock Detection - Resolved

again   Tom Mercadante Oracle Certified Professional -Original Message-From: Mercadante, Thomas F [mailto:[EMAIL PROTECTED]]Sent: Friday, June 22, 2001 3:48 PMTo: Multiple recipients of list ORACLE-LSubject: RE: Deadlock Detection Anita & Riyaj,   Thank

RE: Deadlock Detection - Resolved

tiple recipients of list ORACLE-LSubject: RE: Deadlock Detection - Resolved All,   thanks to Anita, Waleed, Riyaj, Vladimir and Ravinder for pointing me to Bug #132899 in regard to my Deadlock problem.   I upgraded the database from release 8.1.6 to 8.1.7.1 (