Bulk Loading

Bulk Loading is technique  to load the data in inromatica.

You can enable bulk loading when you load to DB2, Sybase, Oracle, or Microsoft SQL Server.If you enable bulk loading for other database types, the Integration Service reverts to a normal load.The Integration Service invokes the database bulk utility and bypasses the database log. Without writing to the database log, however, the target database cannot perform roll-back you must specify a normal load for data driven sessions. When you specify bulk mode and data driven, the Integration Service reverts to normal load.For Sybase and DB2 targets, the Integration Service ignores the commit interval and commits data when the writer block is full. For Microsoft SQL Server and Oracle targets, the Integration Service commits data at each commit interval.

Note:

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. For more information, see Relational Database Connections.

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 datatype, 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.