RE: determining bind values in deadlock situations

  • From: "Barun, Vlado" <Vlado.Barun@xxxxxxx>
  • To: "yong321@xxxxxxxxx" <yong321@xxxxxxxxx>
  • Date: Tue, 3 Mar 2009 16:39:33 -0500

To get all the SQL's apply patch 4441119.

V$sql_bind_capture only captures bind values every 15 minutes for a statement, 
so in situations where the bind values change frequently, this is no use...

Regards,
 
Vlado Barun, M.Sc.
Sr. Manager, Database Engineering and Operations
Jewelry Television
Mobile: 865 335 7652
Email: vlado.barun@xxxxxxx


-----Original Message-----
From: Yong Huang [mailto:yong321@xxxxxxxxx] 
Sent: Tuesday, March 03, 2009 1:19 PM
To: Barun, Vlado
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: determining bind values in deadlock situations

> There is no trace file generated for a deadlock in udump on any of my RAC 
> nodes...

Vlado,

In RAC, you need to check lmd trace files in bdump for the deadlock trace.

Bind variable values are not available in the trace. In fact, if the involved 
sessions are all on the same node, even the SQL is not in the trace. If you do 
get the SQL, you may be able to find the SQL in v$sql% view(s), and may find 
the bind variable value in v$sql_bind_capture.

Yong Huang


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

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 03-2009