Problem With SQL*Loaader In Direct Path Mode And Referential Partitioning

(Doc ID 789671.1)

Last updated on OCTOBER 25, 2017

Applies to:

Oracle Server - Enterprise Edition - Version: and later   [Release: 11.1 and later ]
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version:


Issue with direct loading for tables uses Referential Partitioning. The indexes do not populate for several of the tables when using direct path loading. This applies to global or local primary key indexes.

For global indexes it can be fixed by disabling and enabling the constraint,but for local index the constraints actually need to be dropped and recreated.


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