Unique Index Is Going Unusable State After Data Loading Using SQL*Loader (Doc ID 2184469.1)

Last updated on JANUARY 19, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.

Symptoms

Index (unique) state changing to unusable status after data loading using SQL*Loader. The steps below are executed to load the data:

1/ disable constraint
2/ load data using SQL*Loader
3/ remove duplicate records
4/ enable constraint

The execution of step 3 fails due to an index in unusable state:

Checking the available indexes and their status from dba_indexes, we have:

INDEX_NAME INDEX_TYPE STATUS TABLE_NAME
TN_WHLSL_RTL_CD1_PK NORMAL NORMAL UNUSABLE TN_WHLSL_RTL_CD1
TN_WHLSL_RTL_CD0_PK NORMAL NORMAL VALID TN_WHLSL_RTL_CD0

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms