RE: How to know the stats is corrupted

From: Powell, Mark <mark.powell2_at_hp.com>
Date: Wed, 1 May 2013 14:07:43 +0000
Message-ID: <1E24812FBE5611419EFAFC488D7CCDD1186AB248_at_G6W2491.americas.hpqcorp.net>

When we were on 9.2.x we got better results using analyze than we did using dbms_stats. I would use one of the other based on which produces the best overall results for your environment. When we upgraded to 10g we went with the Oracle provided statistics collection process. We had to tune only a couple of processes as a result of the upgrade.

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of breitliw_at_centrexcc.com Sent: Tuesday, April 30, 2013 4:51 PM
To: David Fitzjarrell; K R
Cc: Oracle-L_at_freelists.org
Subject: Re: How to know the stats is corrupted

Yes, mixing analyze and dbms_stats.gatherxxx can cause problems. Use only dbms_stats. Also, export your stats before gathering. That way you can restore them if the new stats cause problems.

On Tue, 30 Apr 2013 13:41:20 -0700, K R <kp0773_at_gmail.com> wrote: thanks Everyone .
> the version is 9.2.0.4 and running on solaris 9 . We gather the stats
> using analyze most of the time and in some time we use dbms_stats to
> gather stats. Could it be that we should be only using analyze and not
> dbms_stats . or is it that mixing analyze and dbms_stats can cause the
> issue.
>
> the result we observe once in a while lot of physical reads/scattered
> read full tablescan , library cache pin goes up by 100% . . and then
> we end up deleting stats and again running it
>  

  --
Wolfgang Breitling
Centrex Consulting Corporation

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


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

Received on Wed May 01 2013 - 16:07:43 CEST