Re: library cache lock | transaction enqueue lock

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

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<1023980041.690.0.nnrp-14.9e984b29_at_news.demon.co.uk>...
> If you look in $ORACLE_HOME/rdms/admin
> for the script utllock.sql, this will create a couple
> of views of library cache locks (and others) with
> names like dba_kgllock and dba_lock_internal.
>
> Next time you have a session waiting for a
> library cache lock, check v$session_wait for
> the p1 or p2 value, and compare it with the
> lock identifiers in the internal lock views.
> This could give you an important clue about
> which object is the root cause of the problem.
>
>
> --
> Jonathan Lewis
> http://www.jlcomp.demon.co.uk
>
> Next Seminars
> UK June / July
> Australia July / August
> http://www.jlcomp.demon.co.uk/seminar.html
Received on Thu Jun 13 2002 - 14:32:05 CDT