I know you can hint a fast full scan. I have run into cases lately where depending on circumstances Oracle will use an index, but use a sub-optimal type of index scan with dramatic differences in performances.
This is on 9.2. Any hints for forcing an 'index range scan'. Anything stronger than a 'hint'. Something like 'do it because I said so'. This only happens occasionaly, so Id just like to know if it exists for future reference. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: <[EMAIL PROTECTED] INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
