Re: library cache lock | transaction enqueue lock

True on both counts.

I always have to look up the details before I do this sort of thing, so I often get names wrong (or "differently right" as it may soon become).

I actually tend to use the one which I think is called dba_kgllock to start with, as it is the minimal view without the extra UNIONS, joins and garbage - there is also the benefit that when trying to track the problem the WHERE clause is dictated by one of the
parameters of the session wait - although IIRC you could just restrict by session id to keep it simple.

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

Next Seminars
        UK            June / July
        Australia      July / August
http://www.jlcomp.demon.co.uk/seminar.html

Yong Huang wrote in message ...


>Jonathan,

>

>I assume you meant catblock.sql. utllockt.sql (note the "t") gives you

>a tree-like lock graph, for enqueue locks only, not library cache

>locks.

>

>One caveat about dba_lock_internal. It's very useful but it gives you

>too much if you don't have a where clause when you select (of course).

>But when you add a where clause that is slightly complicated, the

>query never returns. I had to restrict with one condition and spool to

>a text file, then search the file to find something I need. I think I

>had this problem on 8.1.6, maybe 8.1.7.

>

>Yong Huang

>