Re: deadlock trace interpretation

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Mon, 7 Oct 2002 18:34:48 +0100
Message-ID: <ansgjd$mkg$1$8302bc10@news.demon.co.uk>

The waiting session, blocking session addresses are just saddr from v$session for the two relevant sessions.

I can't get an 8.1.7 system to emulate the problem at present, so I can't check it, but I think the object handle will map to kglhdadr in x$kglob.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____USA__________November 7/9   (Detroit)
____USA__________November 19/21 (Dallas)
____England______November 12/14

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html





Ted Chyn wrote in message
<44a19320.0210070825.5a48b18c_at_posting.google.com>...


>jonathan, thanks for the reply. the plateform deadlock occurs is 64

>bits HP UX and 64 bits oracle 8.1.7.4.

>Can you shed more light on following questions ?

>

>2. how to translate object handle (c000000020a80868),

>                     waiting session(c0000000044de890),

>                    block session(c000000006f10a70)

>  to object_id or object name and more meaningful session number ?

>

>

>regards

>

Received on Mon Oct 07 2002 - 12:34:48 CDT