Re: How to know the stats is corrupted
From: <breitliw_at_centrexcc.com>
Date: Tue, 30 Apr 2013 14:50:43 -0600
Message-ID: <20130430145043.6xjbuki8kc084o4w_at_webmail.telushosting.com>
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.
Date: Tue, 30 Apr 2013 14:50:43 -0600
Message-ID: <20130430145043.6xjbuki8kc084o4w_at_webmail.telushosting.com>
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-lReceived on Tue Apr 30 2013 - 22:50:43 CEST