Re: Deadlock question

Your deadlock was an ORA-04020 deadlock, not an ORA-00060. This is a library cache issue involving x$kglpn, not a pure data issue involving v$lock.

I can't explain what might have cause the problem in your case - 4020 often means
a coding bug in the Oracle kernel.

If you had looked at v$session_wait, you would (probably) have seen that another
user was waiting for event

    library cache lock
    library cache pin
or perhaps

    library cache load lock

If you had looked in x$kglpn (as sys) you would probably have been able to connect the wait parameters to one of the objects pinned.

There is a script in $ORACLE_HOME/rdbms/admin (dbmslock.sql I think) that creates a couple of view with names like dba_kgl_lock, and dba_lock_internal which exposes library cache locking issues like this.

--
Regards

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

Coming soon a new one-day tutorial:
Cost Based Optimisation
(see http://www.jlcomp.demon.co.uk/tutorial.html )

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

____England______January 21/23
____USA_(CA, TX)_August


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





Jan Gelbrich wrote in message ...


>Hello, this time I would like to ask what I might be missing about

>deadlocks:

>

>SQL> truncate table testtimes_advertizements;

>truncate table testtimes_advertizements

>               *

>FEHLER in Zeile 1:

>ORA-04020: Deadlock festgestellt beim Versuch, Objekt

>310161426609561345801008232312 zu sperren

>(=failed)

>