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
- Brief introduction into Materialized Views
- Voting Disk and OCR in 11gR2: Some changes
- adrci: A survival guide for the DBA
- Oracle HA Architecture
- Data Guard
- Turning Flashback Database on & off with Instance in Status OPEN
- Use RMAN to create your standby database without a previous backup
- No Smart Scan with AUTO_SAMPLE_SIZE
- 11gR2 RAC Architecture Picture
Search inside this Blog
- #ukoug_tech13 3e 10g New Features 11g New Features 12c New Features ABMR Active Data Guard ADO adrci advert ASM auditing AWR Backup & Recovery Brief Introduction Data Guard Data Warehouse DBA JTA dbms_monitor dbms_redefinition DBMS_RLS dcli DOAG2013 exadata Extended RAC external tables fine grained access control flashback flash cache griddisk Grid Infrastructure hcc High Availability ILM logminer LVC Materialized Views Oracle Restart oracle university OU EMEA Newsletter OUG Ireland 2014 OUGN2012 partitioning Performance Tuning RAC Real-Time Query reorganizing RMAN security services smart scan Snapshot Standby storage index TOD Total Recall tracing trcsess ukoug2012 video vpd Webinar whoami X3