Partitioned Index Becomes Unusable After SQLLDR Conventional Load With Truncate Option
(Doc ID 2425156.1)
Last updated on OCTOBER 11, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
After loading data using the TRUNCATE option into a table with LIST PARTITIONS with CONVENTIONAL load method, LOCAL PARTITION INDEX becomes UNUSABLE
Control File: /controlfile
Data File: /datafile
Bad File: /badfile
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 1
Errors allowed: 51
Bind array: 65500 rows, maximum of 40971520 bytes
Continuation: none specified
Path used: Conventional <<<<<<<<<<<
Silent options: FEEDBACK
Table TABLE1, partition PARTITION1, loaded from every logical record.
Insert option in effect for this partition: TRUNCATE <<<<<<<<<<<<<
STATUS INDEX_NAME
------------ -------------------------
UNUSABLE LOCALIDX2
N/A IDX1
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |