In this fifth installment of this series of articles about the non-sharing reasons that prevent Oracle from using an existing execution plan, we are going to dig into two new supplementary reasons: la...
As mentioned in the previous three articles of the series there are sixty-four reasons for which the Oracle Optimizer might decide to hard parse a new execution plan instead of sharing the existing on...
In the previous installment of this series we looked at four reasons from gv$sql_shared_cursor view and explained the situations and criteria for which Oracle is forced to compile a new execution plan...
In an earlier article we discussed two very popular reasons, LOAD_OPTIMIZER_STATS and HASH_MATCH_FAILEDpushing Oracle to refuse sharing an existing execution plan and, thereby, hard parsing a new plan...
For most people troubleshooting SQL query performance problems is a necessity rather than a preference. Very often they are using a trial and error strategy to overcome those frustrating situations. U...
