RE: Date bind variable being peeked, but not used for cardinality estimate

From: "Christian Antognini" <Christian.Antognini@xxxxxxxxxxxx>
To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
Date: Wed, 23 Sep 2009 09:01:01 +0200

Hi Brandon

> I ran a 10053 trace and it looks like Oracle is not really
> peeking at the variables for some reason even though they
> are shown in the 10046 trace and v$sql_bind_capture.

The variables shown in the 10046 trace and in v$sql_bind_capture are not
related to bind peeking. 
However, the 10053 trace provides you the information you are looking
for.

> Sorry to be vague, but maybe check with Oracle Support on this.  I
> recall that some version of the JDBC driver (maybe the thin one) had
> some "complications" with bind peaking.

I'm aware of this limitation (see page 25 of TOP):

"Bind variables peeking is not supported by the JDBC thin driver
distributed with Oracle9i. This restriction is documented in MetaLink
note 273635.1."


HTH
Chris Antognini

Troubleshooting Oracle Performance, Apress 2008
http://top.antognini.ch


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

Follow-Ups:
- RE: Date bind variable being peeked, but not used for cardinality estimate
  - From: Allen, Brandon

RE: Date bind variable being peeked, but not used for cardinality estimate

Other related posts: