Re: How to identify index range scan ?

From: Richard Foote <richard.foote_at_bigpond.com>
Date: Thu, 3 Apr 2003 23:49:27 +1000
Message-ID: <jOWia.6107$1s1.68896@newsfeeds.bigpond.com>

"Bass Chorng" <bchorng_at_yahoo.com> wrote in message news:bd9a9a76.0304021305.4b5d10b_at_posting.google.com...
> Does anybody know how to identify index range scan from
> any of the v$ views ?
>
> I found index fast full scans (rowid ranges) and
> table scans (rowid ranges)in v$sesstat are not what they appear
> to be. I think they have nothing to do with index range scans.
>
> A bad index range scan (vs. Full table scan) can hurt more than
> anything else, but I found it usually very hard to identify,
> unless you already know the SQL and tkprof it.
>
> Thank.

Hi Bass

Assuming your on 9i (you give no indication), V$SQL_PLAN can be used to very easily find all currently cached execution plans that contain an index range scan (operation and options columns).

Cheers

Richard Received on Thu Apr 03 2003 - 07:49:27 CST