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.
Explain, Exemplify, Empower
When is setting OPTIMIZER_INDEX_COST_ADJ appropriate?
Uwe Hesse, OCM
- adrci: A survival guide for the DBA
- Partitioning a table online with DBMS_REDEFINITION
- Reorganizing Tables in Oracle - is it worth the effort?
- Brief introduction into Materialized Views
- Voting Disk and OCR in 11gR2: Some changes
- Exadata Part IV: Flash Cache
- Turning Flashback Database on & off with Instance in Status OPEN
- Retrieve SQL and Execution Plan from AWR Snapshots
- SQL*Plus output in nice HTML format
- Important Statistics & Wait Events on Exadata
- 11gR2 RAC Architecture Picture
- Result Cache: Another brilliant 11g New Feature
- Auto DOP: Differences of parallel_degree_policy=auto/limited
- Exadata Part III: Compression
- Performance Monitoring: Active Session History at work
- How do NOLOGGING operations affect RECOVERY?
- Dealing with Oracle Database Block Corruption in 11g
- Exadata Part II: Storage Index
- Exadata Part I: Smart Scan
Search inside this Blog
Tags10g New Features 11g New Features ABMR Active Data Guard adrci advert ASM auditing AWR Backup & Recovery Brief Introduction Data Guard Data Warehouse DBA JTA dcli exadata Extended RAC external tables flashback flash cache griddisk hcc High Availability logminer LVC Materialized Views Oracle Restart OU EMEA Newsletter OUGN2012 partitioning Performance Tuning RAC Real-Time Query reorganizing RMAN security smart scan Snapshot Standby storage index TOD Total Recall video Webinar whoami X3
Other Bloggers Posts I Like