Using BATCHSQL

In default mode, the Replicat process will apply SQL to the target database, one statement at a time. This often causes a performance bottleneck, where the Replicat process cannot apply the changes quickly enough compared with the rate at which the Extract process delivers the data. Even with GoldenGate spawning additional Replicat parallel processes, performance may still be a problem.

GoldenGate has addressed this issue through the use of the BATCHSQL Replicat configuration parameter. As the name implies, BATCHSQL segregates similar SQL statements into batches and applies them all at once. The batches are assembled in arrays in a memory queue on the target database server that are subsequently applied.

Similar SQL statements are those that perform a specific operation type (insert, update, or delete) against the same target table with the same column list. For example, multiple inserts in table A will be batched together. Similarly, multiple inserts in table B will form...