Re: dbms_stats.gather_table_stats only calculating stats for first partition of range interval - list composite partitioned table

  • From: Peter Hitchman <pjhoraclel@xxxxxxxxx>
  • To: oracle-l <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 11 Dec 2009 13:07:10 +0000

Hi Greg,
Thanks for the reply. I had got to the point where I hoped this was a bug,
but i was interested to see if I could find anyone else it had been tripped
For the time being I using the dbms_stats.set_ calls to create the stats
that I can by summing from the subpartitions, this has had the desired
impact on the SQL plans.

I take your point about the auto sample size, the reason I had not been
using it was that we started with very soon after it was released
and I was sticking to what I knew worked for this database. But given the
nice research you have done, I have decided that in future I will use the
dbms_stats defaults.

At some point I will have to open a SR with Oracle, to get the official line
on this and then I suspect we will planning to upgrade to 11.2, because that
release has other bug fixes we need.



On Thu, Dec 10, 2009 at 6:57 PM, Greg Rahn <greg@xxxxxxxxxxxxxxxxxx> wrote:

> I'm unable to find the exact bug (work with Oracle Support if you
> really want it) but my suggestion would be this:
> Upgrade to and then apply patch 8318020 for dbms_stats.
> There is a significant number of fixes in and it has been a
> pretty stable release IMHO and it fixes quite a number of bugs found
> in
> On Thu, Dec 10, 2009 at 10:17 AM, Greg Rahn <greg@xxxxxxxxxxxxxxxxxx>
> wrote:
> > What you are observing is a bug in - it does not reproduce in
> >  Let me see if I can find the bug.
> --
> Regards,
> Greg Rahn



Other related posts: