Ryan, the problem you are talking about is an 8i problem. Version 9,
especially 9.2
developed so called peeping Tom feature which makes optimizer peek into the
bind variables
for the SQL the first time SQL is executed. Values of those bind variables
are then
used to compute a plan.
--
Mladen Gogala
A & E TV Network
Ext. 1216
> -----Original Message-----
> From: ryan_gaffuri_at_comcast.net [mailto:ryan_gaffuri_at_comcast.net]
> Sent: Wednesday, November 17, 2004 11:07 AM
> To: oracle-l_at_freelists.org
> Subject: histograms, buckets, and bind variables
>
>
> I could have swarn I read that if you use bind variables
> oracle ignores histograms. We are noticing different query
> plans based on the number of buckets our histograms have
> while our queries are using bind variables.
> One of the guys did a 10053 trace and added up the cost
> oracle is calculating and it is changing based on number of
> buckets even when bind variables are used.
>
> anyone else notice this?
>
> --
> http://www.freelists.org/webpage/oracle-l
>
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Nov 17 2004 - 10:47:59 CST
