Inspired by Dominic Brooks’ last post on SQL Plan Management choices, I decided to do the same work about my thoughts on Adaptive and Extended Cursor Sharing triggering mechanism:
Once a cursor is bind aware and subject to an eventual plan optimization at each execution keep a careful eye on the number of cursors the Extended Cursor Sharing Layer are going to produce
Looks good
Comment by Dom Brooks — August 13, 2015 @ 9:21 am |
[…] introduced by Oracle starting from release 11g. Simply put, this feature aims to compile, for a bind aware cursor, an optimal execution plan for each query execution. Extensive details about this feature can be […]
Pingback by Why my execution plan has not been shared – Part I - Oracle - Oracle - Toad World — April 26, 2016 @ 8:46 pm |
[…] In order for the above sql_id to be bind aware and get a new optimal execution plan at each execution, it needs to be executed once again (more details can be found here): […]
Pingback by AWR and superfluous historical statistics | Mohamed Houri’s Oracle Notes — September 28, 2016 @ 6:11 pm |