Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

So I recently updated an Oracle Database 10g from 10.2.0.3.0 to 10.2.0.4.0, as advised by Oracle Support, due to stability issues (a known issue under some systems where the instance would freeze randomly under high load).

After applying the patch, stability problems are gone, but queries are A LOT slower because there are constant FULL SCANS on tables, even though I recalculated statistics for all tables in all schemas and the indexes are apparently OK. I also set the optimizer version value to the previous one (this was advised by Oracle Support too), but it hasn't improved so far.

Any ideas on this?

share|improve this question
    
What does Oracle support have to say about this issue? –  jscott Apr 26 '12 at 23:40
    
They made me drop & recalculate statistics of two tables (not the only ones, but as an example) that are affected by this issue. I also rebuilt the indexes. However, the execution plan is still the same. It just skips the index and proceeds to a full scan, as if it had less cost. I updated the ticked and I am waiting for an answer now. –  Joan Serra Apr 27 '12 at 15:49
    
I have also set optimizer_features_enable value back to 10.2.0.3.0 –  Joan Serra Apr 30 '12 at 15:35

1 Answer 1

up vote 0 down vote accepted

Finally it looks like the problem was caused by poorly optimized SQL. Also it seems like the instance only did full scans only when the cost of these was inferior to the cost of an index scan, so everything is apparently OK.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.