Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: event= to capture deadlock debug info
Hi All,
I think Jim is using the term "deadlock" loosely. He appears to be speaking of a hang.
The normal recommendation for
diagnosing the cause of a hang is to take two 'systemstate' dumps from different
sessions in quick succession. However,
from 8.1.6 there is a 'hanganalyze' dump that can also be used, and is somewhat more
useful. Be warned, however, that
I've seen it crash an instance once.
@ Regards, @ Steve Adams @ http://www.ixora.com.au/ - For DBAs @ http://www.secularislam.org/call.htm - For Muslims @ http://www.christianity.net.au/ - For all
-----Original Message-----
Sent: Saturday, 20 October 2001 4:03
To: Multiple recipients of list ORACLE-L
Hi James,
setting an event at init/session level would basically dump the error state into an trc file. ora-60 or deadlock by defualt writes a message in alert file and also dumps a large trace in udump.
so why do you want to explicitly set this event? The default behaviour mimicks the same anyways.
hth
Deepak
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Steve Adams INET: steve.adams_at_ixora.com.au Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Sat Oct 20 2001 - 02:08:19 CDT
![]() |
![]() |