Bad plan with partitioned table
Hello !
We have an issue with a sql statement. We have a bad plan generated and I can easily reproduce it
it seems we have a mixture of bad and good plans. We have now locked the good plan using spm
The problem seems to be that we start with the wrong table. We have a case with Oracle Support and
we have been asked to regather statistics with and without histograms and so far it hasn't helped.
If we disable bind peeking it seems to be the good plan
I noticed that if we set O.F.E to 11.2.0.2 we get he good plan, looking att he 10053 traces it seems that