Re: determining bind values in deadlock situations

From: Jared Still <jkstill_at_gmail.com>
Date: Fri, 27 Feb 2009 11:56:43 -0800
Message-ID: <bf46380902271156o2c08d6b4x742cfba0ccbbec51_at_mail.gmail.com>



On Fri, Feb 20, 2009 at 5:33 PM, Barun, Vlado <Vlado.Barun_at_jtv.com> wrote:

> Environment: 10.2.0.3 RAC/ASM on Solaris 10
>
> Iím trying to find an efficient way to get the bind values for statements
> that are involved in a deadlock situation.
>
>

Maybe I am just being particularly dense today, but I can't think of why you would need bind variables to resolve a deadlock.

The ORA-60 deadlock is caused by an application error, typically two different parts of an application causing a deadly embrace by trying to lock the same tables, but in different orders.

The trace file generated by the ORA-60 contains the SQL and the rowid's of the affected rows.

Is there something I am missing?

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Feb 27 2009 - 13:56:43 CST

Original text of this message