GROUPTRANSOPS parameter to control the number of SQL operations that are contained in a Replicat transaction when operating in its normal mode (non-
BATCHSQL). Increasing the number of operations in a Replicat transaction improves the performance of Oracle GoldenGate by:
Reducing the number of transactions executed by Replicat.
Reducing I/O activity to the checkpoint file and the checkpoint table, if used. Replicat issues a checkpoint whenever it applies a transaction to the target, in addition to its scheduled checkpoints.
Replicat accumulates operations from source transactions, in transaction order, and applies them as a group within one transaction on the target.
GROUPTRANSOPS sets a minimum value rather than an absolute value, to avoid splitting apart source transactions. Replicat waits until it receives all operations from the last source transaction in the group before applying the target transaction.
For example, if transaction 1 contains 200 operations, and transaction 2 contains 400 operations, and transaction 3 contains 500 operations, the Replicat transaction contains all 1,100 operations even though
GROUPTRANSOPS is set to the default of 1,000. Conversely, Replicat might apply a transaction before reaching the value set by
GROUPTRANSOPS if there is no more data in the trail to process.
Table 3-33 Replicat GROUPTRANSOPS
|Source Transactions (assumes same table and column list)||Replicat transaction in normal (GROUPTRANSOPS) mode|
GROUPTRANSOPS to an arbitrarily high number because the difference between source and target transaction boundaries can increase the latency of the target data.
(Oracle only) For an integrated Replicat,
GROUPTRANSOPS is effective only when the integrated Replicat parameter
PARALLELISM is set to 1.
Nonintegrated Replicat: 1000 operations, Integrated Replicat: 50 operations