Oracle Data pump scenarios that do not use direct path loading

Situations in which Direct Path Load are not used

If any of the following conditions exist for a table, then Data Pump uses external tables rather than direct path to load The data for that table:

• A global index on multipartition tables exists during a single-partition load. This includes object tables is partitioned.

• A domain index exists for a LOB column.

• A table is in a cluster.

• There is an active trigger on a preexisting table.

• Fine-grained access control is enabled with insert mode on a preexisting table.

• A table contains BFILE columns or columns of opaque types.

• A referential integrity constraint is present on a preexisting table.

• A table contains VARRAY columns with an embedded opaque type.

• The table has encrypted columns.

• The table into which data is being imported are a preexisting table and at least one of the following conditions exists:

  • There is an active trigger

  • The table is partitioned

  • Fine-grained access control is in insert mode

  • A referential integrity constraint exists

  • A Unique index exists

• Supplemental logging is enabled and the table have at least one LOB column.

• The Data Pump command for the specified table used the QUERY , SAMPLE , or REMAP_DATA parameter.

• A table contains a column (including a VARRAY column) with a datatype and the version of the time TIMESTAMP WITH TIME ZONE zone data file is D Ifferent between the export and import systems.