Re: Vs: Re: Viewing bind variable values in 10g - Any suggestions?

My understanding from a conversation with a cbo developer at OOW was that bind values are captured only at first parse and subsequently only sampled (again no guarantees), apparently when it falls outside of column hi/lo values.

John

On 11/7/08, Jared Still <jkstill_at_gmail.com> wrote:
> On Thu, Nov 6, 2008 at 10:29 AM, Allen, Brandon
> <Brandon.Allen_at_oneneck.com>wrote:
>
>> Just a couple things to add - you might want to take a look at
>> dba_hist_sqlbind (if you have a Diagnostics Pack license) if you're
>> interested in older bind variables. I think the way v$sql_bind_capture
>> and dba_hist_sqlbind works is that they only capture the bind variables
>> at hard parse time since these are the only variables that are peeked by
>> the CBO in order to determine the optimal execution plan.
>>
>
> As we are not licensed for any of the diag packs, I modified statspack
> to get v$sql_bind_capture values, and run statspack at level 6.
>
> It has proven somewhat effective, though it will require more space
> for the statspack tables.
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
>

-- 
Sent from my mobile device

John Kanagaraj <><
http://www.linkedin.com/in/johnkanagaraj
http://jkanagaraj.wordpress.com (Sorry - not an Oracle blog!)
** The opinions and facts contained in this message are entirely mine
and do not reflect those of my employer or customers **
--
http://www.freelists.org/webpage/oracle-l