Re: What index access path does INDEX_SS yield ?

Jonathan Lewis wrote:

> ... as soon as you use the index_ss() hint, it forces Oracle
> to cost for a skip scan on every single index - even the
> ones where a 'real' skip scan is impossible ... because a
> range/full scan is only a special case of a skip scan.
>
> If, after following this directive, the cost for an index
> full scan on a 'silly' index is less than the cost of using
> an index with a "genuine" skip scan capability, then Oracle
> has to use the "silly" index.

This explanation is both plausible and enlightening, thanks!

• JH