Title: RE: analyze after truncate
Hello,
 
Oracle 8.1.7.4 on HP-UX 11i
 
A week ago, we replaced 'analyze table ... estimate statistics sample 10 percent' with dbms_stats.gather_schema_stats('x', estimate_percent=>10, cascade=>true, degree=>4, method_opt=>''for all indexed columns size 2')
 
Performace is good against partitioned tables but not for non-partitioned tables.
 
Saw a note in Metalink that its better to do the above with 'cascade=>false' and then do a gather_index_stats separately.
 
In my tests, I see that 'analyze' makes the CBO use an index while dbms_stats is making the CBO to use a FTS instead.
 
Have you faced any similar issues?
 
 
TIA
Prakash

Reply via email to