Handling statistics for a column with ever increasing or decreasing values...

(Doc ID 877645.1)

Last updated on FEBRUARY 03, 2017

Applies to:

Oracle Server - Enterprise Edition - Version: to - Release: 10.1 to 11.1
Information in this document applies to any platform.


Bad sql plans are being intermittently chosen, depending on the bind variables passed or peeked.  When a bad plan is traced, it does appear to be lower cost in the 10053.  The culprit is a column in the where clause with a bind that contains a value that is outside of the known range of values in the statistics.


Data is inserted frequently outside of the max/min value of the statistics and that same new data is frequently queried before regathering of statistics on the table.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms