Re: how to dump and comprehend a rollback block

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,

On Tue, 01 Jul 2003 22:46:34 +0200, Sybrand Bakker <gooiditweg_at_sybrandb.demon.nl> wrote:

>If you suspect it is sql, you can easily identify the sql by linking
>the addr column of v$transaction back to the taddr column of
>v$session. The sql_address and the sql_hash_value of v$session point
>to the offending statement.
>I have to look up the info to dump blocks, but I'm not sure it is
>really useful. The lock info is maintained in data blocks.

.......
We use Oracle 8.1.7.4 on Solaris 2.7 boxes remove NSPAM to email Received on Tue Jul 01 2003 - 16:21:21 CDT