RE: Tx - row lock contention after implementing transaction management in application server

You could do a 10046 trace at level 4 (binds) or 12 (binds+waits) and the trace 
file will contain the bind variable values.

-Mark

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of dd yakkali
Sent: Tuesday, May 26, 2009 2:42 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Tx - row lock contention after implementing transaction management in 
application server

Hello everyone,

After our application folks implemented transaction management in the app, I am 
seeing a bunch of seesions waiting with "Tx - row lock contention" on an insert 
statement. we found that the parent table insert is not commited and hence the 
child record insert is hanging as both these statements are using different 
oracle sessions for some reason. This continues for eternity, until the app 
server is killled and restarted.


Sun Java Enterprise Server, hibernate, oracle 10.2.0.4 RAC.


Now here is the question: Our java app server folks are asking me to give them 
bind variable values of the statement that is hanging. We have a connection 
pool which is 132 connections size. Is there any way to get the bind variable 
values after the fact, i.e while it is waiting for the parent to commit?



Thanks
Deen

Other related posts: