Re: Bind variable peeking and Dynamic sampling

Brandon,

To ALWAY_PEEK is to parse always, right?

Using DBMS_RLS, attaching a policy to the desired table - may be with a
sequence, so that the sql is different each time - you can have different
SQL each time. This will cause hard parsing and so ALWAYS_PEEKING.

I do not take credit to this novel idea. Tanel Podar presented a marvellous
presentation in this year's HotSOS covering this.

For me, my oneliner script no_peek.sql has met the needs.
alter session  set "_optim_peek_user_binds"=false;

HTH,
Shiva

On 5/8/07, Charles Schultz <sacrophyte@xxxxxxxxx> wrote:


Good question. Some things, like Database Replay, will be a separate
Database Option, but I am not sure if that applied to the whole kit and
caboodle or not.

On 5/8/07, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote:
>
>  Cool, thanks Christian and Charles for the preview!  I'm looking
> forward to the new features, but I'm guessing they will require a Tuning
> Pack license - did they mention that at Collaborate?
>

--
Charles Schultz

Other related posts: