Re: strange dead lock on clob column

"lsllcm" <lsllcm_at_gmail.com> wrote in message news:0f39afa2-03d4-4c1f-8dee-3a2e8a14f079_at_d27g2000prf.googlegroups.com...
> Hi Jonathan,
>
> Thank you, but why the objn is another table based on objn = 36921
>
> Session 108: obj - rowid = 00009039 - AAAJA5AAoAAAAAAAAA
> (dictionary objn - 36921, file - 40, block - 0, slot - 0)
> Session 145: obj - rowid = 00009039 - AAAJA5AAoAAAAAAAAA
> (dictionary objn - 36921, file - 40, block - 0, slot - 0)
>
> Thanks

Notice that the block number is zero in both cases, this is a strong hint that the numbers are invalid.

Once upon a time, the relevant columns v$session were only set when you were waiting for a row lock - but somewhere in recent versions of Oracle the columns were also used to indicate the culprit in other waits. Sometimes the values are not cleared down after the wait is over - so it's possible that the number reported here are left over from an earlier wait.

-- 
Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com

Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html

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