My Oracle Support Banner

Data Inserted Into Wrong Partition Or ORA-14400 Using SQL*Loader With Direct Path (Doc ID 970917.1)

Last updated on OCTOBER 01, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.1 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.

Symptoms

SQL*Loader loads records into wrong partition, or, returns error:

ORA-14400: inserted partition key does not map to any partition

depending on which platform the load was started, like:

On AIX: SQL*Loader direct path load will incorrectly load a record into wrong partition.
On Solaris: SQL*Loader raises an error instead of record being loaded into wrong partition:

Record 393: Rejected - Error on table VLS_TRANS_MONETARY_LOAD.
ORA-14400: inserted partition key does not map to any partition

However, run the load again of the bad record and it will be inserted into correct partition.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.