Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Unable to find SQL executed by blocking session
Raj,
I think what you're seeing is expected behavior.
If session #1 locks a row:
update tab_a set col_b=3D'hi there' where col_a=3D1;
then that SQL completes execution and the SQL address and hash value in V$SESSION will no longer point to that statement. But, until that session commits the transaction, the TX=20 lock is held.
So, it should be easy to identify a blocking session, and even the specific locked row (if it's blocking another session), but it's (I think) not possible to identify the specific statement that was executed that create that particular row-level lock.
Hope that helps,
-Mark
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of rjamya
Sent: Friday, October 15, 2004 11:36 AM
To: sfaroult_at_roughsea.com
Cc: Oracle Discussion List
Subject: Re: Unable to find SQL executed by blocking session
GV$ ... always.
Raj
On Fri, 15 Oct 2004 17:44:33 +0200, Stephane Faroult
<sfaroult_at_roughsea.com> wrote:
> =20
>=20
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Fri Oct 15 2004 - 10:42:06 CDT