The main benefit of Integrated Replicat is the parallel processing. Integrated Replicat can automatically check dependencies and auto tune parallelism based on the workload. The parallelism is controlled by two parameters in the replicat parameter file PARALLELISM and MAX_PARALLELISM .
- PARALLELISM is the minimum number of parallel apply processes. Default is 4.
- MAX_PARALLELISM is the maximum number of apply servers. Default is 50.
- integrated replicat is a two-step process. We know that Classic Replicat directly connects to the target database via OCI (Oracle Call Interface) and delivers the SQL transactions. However, Integrated Replicat process only reads the GoldenGate trail files, constructs logical change records (LCR), and then delivers the LCRs to the Inbound Server. The Inbound Server runs inside the Oracle database, which collects the LCRs, calculates the dependencies, group transactions, and then applies the transactions to the target database. The replicat process still performs data filtering, mapping and transformations but doesn't apply the DML and DDL operations.
- Integrated replicat keeps the transaction boundaries. However, the transactions are applied asynchronously, which means if there is no dependency, the transactions are applied in parallel with random orders to optimize the performance. (Coordinated replicat breaks the transaction boundaries for parallel processing.)
- Integrated replicat automatically check dependencies while coordinated replicat requires you to make sure there is no dependency across replication threads.