The initialization parameter OPTIMIZER_INDEX_COST_ADJ has a certain popularity in the area of Oracle Database Performance Tuning. Especially, it can be used to make the Optimizer favor index access instead of full table scans. But that is not necessarily appropriate – in fact it can have very counterproductive effects on performance. Richard Foote has some very instructive postings about this, especially this one is impressive, in my view.
When is setting OPTIMIZER_INDEX_COST_ADJ appropriate?
- Like uhesse.com on Facebook
I’m speaking
Blog Follower
Recent Comments
Jeyalin Sheeju on Reorganizing Tables in Oracle… Uwe Hesse on Using Flashback in a Data Guar… kurschies on Using Flashback in a Data Guar… Uwe Hesse on orapwd gives OPW-00029 Passwor… laurentschneider on orapwd gives OPW-00029 Passwor… Johannes on Resizing datafiles with Data G… Muhammad Rahman on The Recovery Area: Why it is… eric.hu@sap-perf.ca on Joining Accenture Enkitec… Carlos Roberto Reyes… on FLASHBACK PLUGGABLE DATABASE n… Eric Yen on Partitioning a table online wi… fouedgray on How Partial Indexing helps you… sathish kumar dina j… on Purpose of the Voting Disk for… 
#1 by bernardino on August 26, 2014 - 23:26
buenas articulos
#2 by Nassou on August 23, 2016 - 17:20
I agree, and especially perfectly detailed and explained with consistency.