Re: how to dump and comprehend a rollback block

From: Jaap W. van Dijk <j.w.vandijk.removethis_at_hetnet.nl>
Date: Sat, 05 Jul 2003 10:18:50 +0200
Message-ID: <u62dgvob03r49eji97ls6j39emehu7kv0g@4ax.com>

On Tue, 01 Jul 2003 21:21:21 GMT, andreyNSPAM_at_bookexchange.net (NetComrade) wrote:

>What if there were other sql statements executed after the 'offending'
>statement?
>
>Anyway, unfortunately sql_address and hash_value show zeros, i've
>already tried that, but thanks.
>
>The only lock for the session is a TX lock, and nothing else. the id's
>for TX locks containt rollback info, if I recall correctly, which is
>already given in v$transaction table.
>
>If there is any other way in identifying the TX lock source I could
>use, it would be greatly appreciated.
>
>Thanks,

There are issues involving distributed SELECT's causing TX locks on rollback. Do you use these? Then maybe the following link can put you on track:

http://www.jlcomp.demon.co.uk/faq/dblink_commit.html

HTH, Jaap. Received on Sat Jul 05 2003 - 03:18:50 CDT