Re: library cache lock | transaction enqueue lock

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

Knut Talman wrote in message ...


>Hi,

>

>on an Oracle 8.1.7.3 on Linux database we have the following problem:

>

>An application stops working because of locks. The app has 4 open sessions,

>one session is blocking the others.

>Session 1 waits for a library cache lock and blocks session 2 which waits

>for a transaction enqueue lock.

>Session 1 helds an exclusive transaction enqueue lock which is requested by

>session 2. When I kill session 1 the

>application reconnects to the database and I have the same situation like

>before. Even shutting down the

>application does not solve the problem. All but one session are closed. I

>can't kill the one session with

>"alter system kill session ....", I have to kill the dedictated server

>process. Aftre doing that and restarting the app

>everything works fine until the next blocking lock.

>I know that a library cache lock will happen when I try to use a procedure

>which is just compiling or something

>similar, but the session are just doing updates.

>Does anybody have an idea what's going on here?

>

>Thank you in advance,

>

>Knut

>

>