Re: Hints

There are 2 problems with using  optimizer_index_cost_adj. Tim covered the 
first extensively (it's a problematic parameter). However, the main reason for 
me is that you shouldn't use global parameters to get around a problem with a 
few of sections of code. There are so many other options to control 
optimisation; object stats, histograms, system stats, hints, outlines, profiles 
and baselines to name a few. as well as rewriting the code of course. 

Try not to use the sledgehammer of global change unless you have global 
problems and will see an overall net benefit from such an implementation. 

Regs

Neil Chandler
sent from my phone

On 15 Aug 2011, at 18:13, "MacGregor, Ian A." <ian@xxxxxxxxxxxxxxxxx> wrote:

> It may be that Oracle has incorrect statistics concerning your I/O system,  
> or even if those statistics are good, has still misjudged its capabilities. 
> It may be the OS statistics were gathered at an inappropriate time.  I am of 
> the opinion that Oracle still overrates full table scans as compared to index 
> lookups.   There is an initialization parameter which addresses this.
> 
> optimizer_index_cost_adj
> 
> 
> 
--
http://www.freelists.org/webpage/oracle-l

Other related posts: