Re: Very Strange Query Access Plan

Few questions:
Can you elaborate on the "bad" values? What makes them bad? Are other values (like NDV) non-representative as well? What is your DBMS_STATS.GATHER_* command?

The reason I am asking is I'd like to understand if this was a symptom of a suboptimal DBMS_STATS gather process (meaning non-default options), or if it is more to do with DBMS_STATS itself (using default options).

Also sharing your debug approach would be beneficial for the community. Often times its more about the approach to solving the issue rather than the solution itself.

On 10/2/07, Mercadante, Thomas F (LABOR) <Thomas.Mercadante_at_labor.state.ny.us> wrote:

> Thanks to Alvaro Jose Fernandez & Ric Van Dyke, this is solved. The DENSITY
> and CLUSTER FACTOR values in the user_tab_columns for my database table had
> bad values. These values are calculated by the DBMS_STATS package. I
> manually set these to a much lower figure and my problem went away.

-- 
Regards,

Greg Rahn
http://structureddata.org
--
http://www.freelists.org/webpage/oracle-l