BULKLOAD

Valid For

Replicat

Description

Use the BULKLOAD parameter for an initial load Replicat when using the direct bulk load to Oracle SQL*Loader method. This method passes initial-load data directly to the interface of Oracle's SQL*Loader utility to perform a direct load. A Collector process and trails are not used. Many bulk loading utilities do not support LOB data or have other data type restrictions. Oracle recommends that you consult the appropriate database documentation for a complete list of restrictions. For tables that are not supported by BULKLOAD, use the trail file method of initial loads.

For a complete guide to the methods of loading data with Oracle GoldenGate, see Administering Oracle GoldenGate.

Default

None

Syntax

BULKLOAD  
[LOGGING | NOLOGGING] 
[PARALLEL | NOPARALLEL]
[SKIPALLINDEXES | SKIPUNUSEDINDEX | NOSKIPALLINDEXES]

LOGGING | NOLOGGING

Valid for Replicat for Oracle. LOGGING is the default and enables redo logging for the loaded objects. NOLOGGING increases BULKLOAD performance by disabling redo logging of the loaded objects. Do not specify NOLOGGING for cascading synchronization and multiple master configurations.

However, BULKLOAD must be set to LOGGING if the target is part of a cascading or bi-directional configuration, where a local Extract will capture the loaded objects.

PARALLEL | NOPARALLEL

Valid for Replicat for Oracle. PARALLEL enables BULKLOAD to use multiple load sessions to load the same segment concurrently. NOPARALLEL is the default and disables parallel loading.

SKIPALLINDEXES | SKIPUNUSEDINDEX | NOSKIPALLINDEXES

Valid for Replicat for Oracle. Controls the handling of indexes. NOSKIPALLINDEXES is the default, which allows index maintenance during a direct load. SKIPALLINDEXES skips all index maintenance. SKIPUNUSEDINDEX skips unusable indexes.