When you enable bulk load to Oracle, the Integration Service invokes the standard Oracle client interface with the bulk routines for direct path loads.
Use the following guidelines when bulk loading to Oracle:
Do not define CHECK constraints in the database.
Do not define primary and foreign keys in the database. However, you can define primary and foreign keys for the target definitions in the Designer.
To bulk load into indexed tables, choose non-parallel mode and disable the Enable Parallel Mode option.
Note that when you disable parallel mode, you cannot load multiple target instances, partitions, or sessions into the same table.
To bulk load in parallel mode, you must drop indexes and constraints in the target tables before running a bulk load session. After the session completes, you can rebuild them. If you use bulk loading with the session on a regular basis, use pre- and post-session SQL to drop and rebuild indexes and key constraints.
When you use the LONG data type, verify it is the last column in the table.
Specify the Table Name Prefix for the target when you use Oracle client 9i. If you do not specify the table name prefix, the Integration Service uses the database login as the prefix.
For successful Oracle Real Application Cluster (RAC) failover, the Oracle target load type must be normal. If the target load type is bulk, the mapping fails.
For more information, see the Oracle documentation.