SQL Performance (MOSC)

MOSC Banner

Unoptimized execution plan due to unusable index partition

edited Apr 17, 2014 12:00PM in SQL Performance (MOSC) 1 commentAnswered

Hello All!

I have a partitioned table with local partitioned no unique indexes on its columns.

Data load in this table make some index partition unusable during loading. In this time another users make select from this table. Because of  using bind variables, during select, optimizer choose to skip index with unusable partition and make table full scan. The execution plan become unoptimized. I try to use skip_unusable_indexes=false parameter to force using index but receive error “ORA-01502: index "string.string" or partition of such index is in unusable state” after select from this table.

Why this error occur? Select statement use only those table partition on which index partition is in usable state.

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center