1 Reply Latest reply on Jan 22, 2013 7:23 PM by damorgan

    bad CBO statistics

      Hi All ,

      I've below questions regarding the statistics gathering.Could you please try to answer.

      If the queries performance were acceptable , then the underlying table's stats should not be gathered ( as it may go either ways i.e improve or decrease the performance of the queries,lock_table_stats is a proof for the same) ?.Do you agree?

      How to confirm the queries are performing slow because of the bad CBO statistics.?

      Could you please elaborate the "Test with the RULE hint" from [Burleson's post|http://www.dba-oracle.com/t_sql_tuning_tricks.htm] ?

      Thanks in advance,
        • 1. Re: bad CBO statistics
          The last thing I would recommend you read about any Oracle topic is something from dba-oracle.com. To better understand this point google the following:
          "Kyte" and "Burleson"
          My generic advice, because in Oracle there are very few absolutes, is that before you make decisions with respect to stats and stats collection you determine how Oracle is using the stats. Not collecting stats works well right up until the point-in-time when the table changes enough that the plan it is generating because a problem rather than a solution. Collecting stats always works provided you collect them properly and don't hit a bug.

          The only persons whose advice I would recommend you take on this question, Exadata or not, is that of Jonathan Lewis, Christian Antognini, Tanel Poder, and a few other members of the Oak Table.