We had trouble with analyze during heavy updates.
Something to do with SNAPSHOT TOO OLD.
The instance froze. It is corrected somewhere in 8.1.7.
Oracle will not port the fix to 8.1.6.
We schedule the analyze to work at night and no problems.
Yechiel Adar, Mehish Computer Services
[EMAIL
Well, it has some bugs with GATHER EMPTY and GATHER
STALE on your release. However, I set it in some
clients and it is working fine. As an advice, don't
use those options, reduce the size of the bucket just
to generate statistics quickly, lastly if you decide
against DBMS_STATS, don't run
DBMS_STATS only gathers stats that the optimizer needs. For example, the
CHAIN_CNT field is not updated because the optimizer doesn't need it. I hate
this because now I don't know if the table has chained or migrated rows. The
ANALYZE command still gives you this information.
-Original
Thanks for the advice, Christian, but I'm a little confused. What do you
mean by don't run statistics with analyze
because it doesn't generate any?
Rich Jesse System/Database Administrator
[EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA
Sorry, I haven't explained myself correctly. When you
have first run a dbms_stats to generate on partitioned
tables, analyze doesn't generate any. However, this
applies for compute statistics.
I think this article could explain you better than I:
Doc ID: Note:97207.1
Type: PROBLEM
Status:
Does this apply in 8.1.7. I couldn't tell from the doco.
Kathy
-Original Message-
Sent: Tuesday, February 26, 2002 9:28 AM
To: Multiple recipients of list ORACLE-L
Sorry, I haven't explained myself correctly. When you
have first run a dbms_stats to generate on partitioned
tables,
