This content has been marked as final. Show 2 replies
This is normal and expected - the optimizer is continually being changed/tuned to provide the most efficient execution plan - the plan will vary from version to version depending on the features available in the optimizer for that version, and the amount/type of statistics available in that version.1 person found this helpful
See the "Note" section here - http://docs.oracle.com/cd/E11882_01/server.112/e16638/optimops.htm#i82005
Thanks for the response.
Yeah, I got a bit carried away in the differences to notice if the plan has improved over the releases.
Better stats available -> better/effective plan
I hope this can be validated by using 10053 trace event.