Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Strange results with Oracle 8.1.7 and statistic gathering dbms_stats vs dbms_utility
Daniel Morgan <dmorgan_at_exesolutions.com> wrote in message news:<3D9C6349.5F58B94A_at_exesolutions.com>...
> martin wrote:
>
> > We have a customer with a large app using WebSphere and Oracle 8.1.7.
> > They run:
> > exec dbms_utility.analyze_schema('SAP', 'COMPUTE'); weekly.
> > We recently ran:
> > dbms_stats.gather_schema_stats(ownname=>'SAP';)
> > on our test system and saw HUGE improvements in speed.
> > Why is this? What is the difference between the two.
> >
> > Please help and advise.
> >
> > Martin Folb
> > WGCUSA
>
> Oracle only keeps the dbms_utility_analyze, and the other anlayze
> methods, around for purposes of backward compatibility. They are for all
> intents and purposes desupported and don't handle new features.
>
> But I would suggest, in the future
> dbms_stats.gatehr_schema_stats(ownname=>'SAP', cascade=TRUE)
>
> so that it will also analyze the indexes.
>
> Daniel Morgan
exec dbms_stats.gatehr_schema_stats(ownname=>'SAP', cascade=>TRUE);
the '>' is required there.
Make sure that you don't use a mix of stats gathered by the 2 methods.
also, are you certain that the parameters for 'optimizer%' are the same?
Paul Received on Thu Oct 03 2002 - 22:12:36 CDT