Re: strange dead lock on clob column

On Nov 30, 3:14 am, "Jonathan Lewis" <jonat..._at_jlcomp.demon.co.uk> wrote:
> "lsllcm" <lsl..._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 Lewishttp://jonathanlewis.wordpress.com
>
> Author: Cost Based Oracle: Fundamentalshttp://www.jlcomp.demon.co.uk/cbo_book/ind_book.html
>
> The Co-operative Oracle Users' FAQhttp://www.jlcomp.demon.co.uk/faq/ind_faq.html

I'm sure this is the same problem you told us about last year:

http://groups.google.com/group/comp.databases.oracle.server/msg/beff96edcc7c13ad

isn't it? I reproduced it in 9.2.0.7 and 10.2.0.2 (documented at http://yong321.freeshell.org/oranotes/RowWaitObj%23NotUpdated.txt) I haven't found a bug report for this on Metalink.

Yong Huang Received on Fri Nov 30 2007 - 17:49:02 CST