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

From: Thomas Roach <>
Date: Tue, 26 May 2009 15:08:21 -0400
Message-ID: <>


Look at the view gv$sql_bind_capture. I use it to get bind values.

On Tue, May 26, 2009 at 2:41 PM, dd yakkali <> wrote:

> 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 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

Thomas Roach

Received on Tue May 26 2009 - 14:08:21 CDT

Original text of this message