Try this
- TRANSACTIONS, ROLLBACKS
- This shows the user who's transaction is being rolled back
- If this number, xidusn, is decreasing then the transaction is rolling
back
- If it is increasing then the transaction is moving forward
select
a.sid,
a.username,
b.xidusn rollback_seg_no,
b.used_urec undo_records,
b.used_ublk undo_blocks
from
v$session a,
v$transaction b
where
a.saddr=b.ses_addr;
"John" <john.lehew_at_hp.com> wrote in message
news:938581bd.0304300801.24b2cf97_at_posting.google.com...
| After noticing a SELECT statement that hung on Oracle 8i and Win2K, an
| ALTER SYSTEM KILL SESSION command was issued to kill the session.
|
| After four hours, we tried to TRUNCATE the same table the original
| SELECT statement/session was using; however, it apparently was still
| holding onto the table we were trying to TRUNCATE.
|
| Next we tried ORAKILL. It's been 3 hours since then and the database
| is not under much of a load ( 5% CPU ) and the original session is
| still in its 'KILLED' state.
|
| Is there anything else that can be done?
|
| Thank you,
| John
Received on Wed Apr 30 2003 - 20:37:33 CDT
