Re: Bad execution plan after migrating to exadata ( 12c) from non-exadata (11g)

Hey guys,
just a quick add here.

You should give Pathfinder a try if the execution plan change is related to some optimizer feature or bug fix that was introduced with 12c. Very easy to use and pretty easy to spot :)

• https://github.com/mauropagano/pathfinder
• https://medium.com/_at_FranckPachot/i-fixed-execution-plan-regression-with-optimizer-features-enable-what-to-do-next-ddb99bb7ba15

Best Regards
Stefan Koehler

Independent Oracle performance consultant and researcher Website: http://www.soocs.de
Twitter: _at_OracleSK

> Andy Sayer <andysayer_at_gmail.com> hat am 13. August 2019 um 10:00 geschrieben:
>
> We’re also dealing with a version change, 12c would include many “fixes” that completely removed some query transformations, is that the case here? If you hinted for the old plan (using the full outline), would you even be able to get it? It’s a good idea to make sure you’re running the latest patches where these sorts of things are fixed at a more appropriate granularity.
>  
> Hope this gets you started,
> Andy

--
http://www.freelists.org/webpage/oracle-l