Pl sql clob updating consolidating debts have more money pay need
Also he had a nice script for pulling the hints from V$SQL_PLAN table which I have made use of as well.
This still leaves the optimizer with a lot of flexibility when it comes to choosing a plan.
It also sets up a commonly occurring situation where the fudge factors stop making sense as the statistics change.
Those offered Profiles often have a lightly documented hint (OPT_ESTIMATE) that allows it to scale the optimizer estimates for various operations – essentially it’s a fudge factor.
The problem with this hint is that, far from locking a plan in place, it is locking an empirically derived fudge factor in place.
He commented on my Outlines post last week and recommended I give his post on SQL Profiles a look. One of the things I liked the best about the post was that he created a couple of scripts to pull the existing hints from a statement in the shared pool or the AWR tables , and create a SQL Profile from those hints using the DBMS_SQLTUNE. This makes perfect sense because the hints are stored with every plan (that’s what DBMS_XPLAN uses to spit them out if you ask for them).