RE: Reading UNDO and displaying it in v$session

From: Milen Kulev <>
Date: Thu, 3 Apr 2008 20:28:09 +0200
Message-ID: <00ad01c895b8$7ae0c0d0$>

Hello Brandon,
yes, I am aware of this fact , but my goal was (and is) to write a performance monitoring skript that provides me with the infomation
about sessions details (SID, SPID, WAIT EVENT , Session State, SQL_ID, CHILD_NR tomention a few) and object_id of the the database object beining accesed at the moment. The link below describes actually (this is my understanding, at least) the dependency of ROW_WAIT_ROW# on ROW_WAIT_OBJ#.
Perhaps ROW_WAIT_ROW# is interesting (in combination witn ROW_WAIT_OBJ# and the other ROW_WAIT_*# from V$session) when EVENT='enq: TX - row lock contention' ?  

Best Regards. Milen    

-----Original Message-----
From: [] On Behalf Of Allen, Brandon Sent: Thursday, April 03, 2008 6:33 PM
To:;; Subject: RE: Reading UNDO and displaying it in v$session

Hi Milen,

I believe the purpose of row_wait_obj#, and the other row_wait columns is only to report relevant information when a session is waiting on a blocking lock, i.e. the "enqueue" wait event for a TX (aka Transaction) lock. Here are the column descriptions from the documentation:


Please note the following:

ROW_WAIT_ROW# - Current row being locked. This column is valid only if the session is currently waiting for another transaction to commit and the value of ROW_WAIT_OBJ# is not -1. (emphasis mine)


Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

Received on Thu Apr 03 2008 - 13:28:09 CDT

Original text of this message