Re: query plan, outln, statistics, off topic

Mladen,

   Thanks and I hope you are serious. Freeze statistics is what I thought also as said in #3. There is resistance for this as people say : 'Oracle recommends weekly gather'. And that is probably to take care of data changes.

dbaplus,

   Thanks. I did not know one could add hints when the sql itself is not known. Is it possible for you to give details about the example you implemented. Thanks

dbaplusplus_at_hotmail.com wrote:
> On Apr 15, 5:31 pm, Mladen Gogala <mgogala.SPAM_ME...._at_verizon.net>
> wrote:
> > On Sun, 15 Apr 2007 13:19:07 -0700, renu_p_r wrote:
> > > 1) For plan stability : Meaning I do not want too many surprises with
> > > query plan explain plan : for that one solution is use outline. However
> > > I think that might add overhead. Does anyone have any other input issues
> > > with outline.
> >
> > The best thing for plan stability is not to gather any statistics, once
> > you've gathered it.
> >
> > --http://www.mladen-gogala.com
>
> A major advantage of outln is that if you do not have access to sql
> statement code (i.e., cannot change sql satement), in some cases
> you can add hints to sql using outln and improve the performance. I
> had read about this feature many times and finally got to use
> it in real world. I had a EMC Documentum based Oracle Database. There
> was a sql statement which takes 10-15 minutes, runs many times, cannot
> be improved using indexes. If I could add a hint, its time reduced to
> a few seconds. I had no access to source code, but thanks to outln, I
> could add the magic hint.
Received on Tue Apr 17 2007 - 14:31:34 CDT