Re: silly dbms_stats question
- From: Fuad Arshad <fuadar@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Thu, 30 Apr 2009 13:37:05 -0700 (PDT)
you can always lock the stats so oracle will never change the stats
________________________________
From: "Brady, Mark" <Mark.Brady@xxxxxxxxxxxxxxxxx>
To: Thomas Day <tomdaytwo@xxxxxxxxx>
Cc: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
Sent: Thursday, April 30, 2009 1:49:01 PM
Subject: RE: silly dbms_stats question
>Other than exporting the good stats and re-importing
them daily, is there any way to stop Oracle from marking the stats as stale?
Do you have a particular issue
with this approach? Why doesn’t this work for you?
________________________________
From:Thomas Day
[mailto:tomdaytwo@xxxxxxxxx]
Sent: Thursday, April 30, 2009 7:57 AM
To: yong321@xxxxxxxxx
Cc: Crisler, Jon; oracle-l@xxxxxxxxxxxxx
Subject: Re: silly dbms_stats question
Does Oracle use stale stats for the CBO if fresh stats
aren't available or does Oracle treat stale stats the same as non-existant
stats? Is there a way, other than re-analyzing the table or index, to
keep stats from being marked as stale?
We have tables that are being truncated nightly and then
being re-loaded with data that is 99.99% identical with the previsous
data. (Don't bother telling me that we shouldn't be doing it that
way; I have to play with the cards I'm dealt.) I have the schema stats
locked and the automatic stats job is disabled. (It insisted on computing
new stats on the table when it was at 0 rows.) Oracle is marking the
stats as STALE.
Other than exporting the good stats and re-importing them
daily, is there any way to stop Oracle from marking the stats as stale?
>>> This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for the
addressee. If you are not the intended recipient, do not use the information
in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2
Other related posts: