Take a look at user_tab_columns -
your choice of:
method_opt = 'for columns'
On a quick test on 9.2.0.3 this seems to
leave the columns with null statistics.
(check
select column_name, num_distinct
from user_tab_columns
)
In passing, computing histograms with 75
buckets for all
without effect on my testcase
Thnx,
Jeroen
-Oorspronkelijk bericht-
Van: Jonathan Lewis [mailto:[EMAIL PROTECTED]
Verzonden: Thursday, December 11, 2003 10:49
Aan: Multiple recipients of list ORACLE-L
Onderwerp: Re: analyze problems
Take a look at user_tab_columns -
your choice
Not that he needs it, but I can confirm Jonathan's claim that the
method_opt clause you are using does not collect column statistics:
SQL @delete_table_stats tp1
PL/SQL procedure successfully completed.
SQL @tblstats tp1
Hi,
I'm in the middle of
migrating oracle 7.3.4 to oracle 9.2.0.4
In process of testing we
encounter a big query that is now taking full table scans
Where it
used to take indexes.
When we compare plans this is evidently so,
Optimizer_mode is on both choose, tables and indexes are
.
- Original Message -
From:
Jeroen van Sluisdam
To: Multiple recipients of list ORACLE-L
Sent: Wednesday, December 10, 2003 11:29
PM
Subject: analyze problems
Hi,
I'm in
the middle of migrating oracle 7.3.4 to oracle
9.2.0.4
In
process of testing we
