Re: cursor_sharing setting

What is the _optim_peek_user_binds setting?

In any case, if the warehouse has been running for some time without serious problem, you probably dont want to change that setting without understanding why it was set the way it was to begin with. Of course, the answer is likely to be that it was set that way 10 years ago in oracle 9i and never changed it, but it is still not something to change without testing.

On Mon, Feb 10, 2020 at 11:13 AM Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

> I would not set it anywhere. CS = FORCE is a source of many optimizer
> bugs and is only recommended in case of an emergency, where one needs to
> break the glass first.
>
> Regards
>
>
> On 2/10/20 7:54 AM, l.flatz_at_bluewin.ch wrote:
> > Hi,
> >
> > I would not set cs=forced in a DWH. These a logrunning queries and the
> > plans should be as good as possible.
> > Parse time will normally be a lesser concern.
> > Just to give an example: Bind varaibles for a partition key should
> > inhibit from partion stats being used on parsing.
> >
> > Regards
> >
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

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