Valid for

Replicat

Description

Use GROUPTRANSOPS to group transactions when applying changes to the target database. Small transactions from the source database are grouped into a single large transaction on the target side, which can result in significant performance benefits. In general, GROUPTRANSOPS speeds up processing for smaller transaction sizes.

With GROUPTRANSOPS, the integrity of the original transaction is preserved at the target. GROUPTRANSOPS controls the frequency of checkpoints written to keep track of activity, minimizing I/O (a checkpoint is written and flushed to disk after each transaction completes).

Default

500

Syntax

GROUPTRANSOPS count

count

Specifies the number of source DML change records that are combined into a single transaction to be applied at the target. For non-audited Extract, the source produces a single DML record per transaction. Therefore, a count of 500 implies 500 records. For TMF-based capture, the number of DML records per transaction vary and checkpointing occurs after reaching this count value and on the next transaction boundary in the source data. Using a higher count causes less checkpoint processing and allows for faster access, but setting this count too high can cause locked rows, pages, and/or error 35’s.