Performance - EBS (MOSC)

MOSC Banner

Index Only Scan On Partitioned Table

edited Jul 5, 2011 12:10AM in Performance - EBS (MOSC) 3 commentsAnswered
If I have a table with an index on a column and select using only that column, it will only interogate the index (can be seen in an explain plan of eg1). Which is expected as the data is in the index so does not need to look at the table as well

e.g. 1

 ( select reportable_id from vertex_report.cash WHERE reportable_id = '12345'; )

Plan
SELECT STATEMENT CHOOSE SELECT STATEMENT CHOOSE Cost: 3 Bytes: 36 Cardinality: 3
  1 INDEX RANGE SCAN INDEX VERTEX_REPORT.I$CASH$REPORTABLE INDEX RANGE SCAN INDEX VERTEX_REPORT.I$CASH$REPORTABLE Cost: 3 Bytes: 36 Cardinality: 3

--

However, if the table is partitioned, say on date, the query interogates both the partitioned index and the partition of the table (can be seen in an explain plan of eg2). Why does it not use just the partitioned index only as the data is in the partitioned index. Why does it also need to go to the table partition associated with that partitioned index. Can just the index scan be forced?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS Performance Tags

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center