Using SQL*Loader WIth Parameter NO_INDEX_ERRORS=TRUE Causes An Inconsistent Table State
(Doc ID 1396694.1)
Last updated on OCTOBER 10, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
You started SQL*Loader in direct path mode with parameter NO_INDEX_ERRORS=TRUE and observed an inconsistent table state after the load. The next test case demonstrates this:
Note: This occurs *only* when ERRORS=<n> is specified. It seems, when the count of allowed errors is exceeded, the index remains loaded but not the table. This explains count 0 in table but ORA-1 from index when an already existing value is again inserted.
If you take out ERRORS=0 from control file above, then the behavior is the expected one:
- the count from table shows 1 row
- the index is loaded with 1 key
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 |
| References |