ANSWER - 10g, blocking session is null when locking occurs on other node.

Just to follow up, Oracle support said this is a know issue and will be = fixed in 10g. release 2.=20

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Fedock, John (KAM.RHQ)
Sent: Thursday, April 14, 2005 10:04 AM
To: Oracledba_at_Lazydba. Com (E-mail); Oracle-L (E-mail) Subject: 10g, blocking session is null when locking occurs on other node.

I am testing a new 10g RAC (2 node) system on HP-UX. I am testing how = to diagnose locking issues. On node 1, I update a table. In=20 another session on node 1, I update the same table and this session = waits as expected. In v$session I can see the enq TX wait and now in 10g = I can even see the session that is causing the block (in the = blocking_session column - very cool). If I open a session on node 2, and = also update that same table (as on node 1), I can see the enq TX wait, = but the blocking_session status is null and the blocking_session_status = is 'GLOBAL'. It seems to me that the blocking_session is missing on this = second node during an TX situation.=20
When this situation occurs, I can easily see that a session is being = blocked ... if it has status of GLOBAL, I can assume it is being blocked = by a session on the other node, but I have no way of knowing what SID is = causing the block.=20

Is this expected behaviour? I opened a TAR with Oracle and they could = reproduce, but have not said if this was expected or not.

TIA. John

   John Fedock
   "K" Line America

--

http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Mon Apr 25 2005 - 16:22:57 CDT