Types of Replicat

The Replicat process can be configured in the following modes (also referred to as Replicat types):

• Classic Replicat: In classic mode, Replicat is a single-threaded process that uses standard SQL to apply data to the target tables. See Classic Replicat for more details.

• Coordinated Replicat: In this mode, the Replicat process is threaded. One coordinator thread spawns and coordinates one or more threads that execute replicated SQL operations in parallel. A coordinated Replicat process uses one parameter file and is monitored and managed as one unit. See Coordinated Replicat for more details.

• Integrated Replicat: In this mode, the Replicat process leverages the apply processing functionality that is available within the Oracle Database. Within a single Replicat configuration, multiple inbound server child processes known as apply servers apply transactions in parallel while preserving the original transaction atomicity. See About Integrated Replicat for more details.

• Parallel Replicat: Is a new variant of Replicat that applies transactions in parallel to improve performance. Parallel Replicat only supports replicating data from trails with full metadata, which requires the classic trail format. It takes into account dependencies between transactions, similar to Integrated Replicat. See Parallel Replicat for more details. Parallel Replicat is available in non-integrated (classic) and integrated mode.

• Initial Load Replicat: In this mode, when you set up Oracle GoldenGate for initial loads, the Replicat process applies a static data copy to target objects or routes the data to a high-speed bulk-load utility. See Precise Instantiation for Oracle Using Initial Load Extract for more details.