Load Balancing Across Multiple GoldenGate Processes
Last updated on FEBRUARY 21, 2017
Applies to:Oracle GoldenGate - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11.1.1 to 12.2]
Information in this document applies to any platform.
There are times when a single GoldenGate process (Extract, Data Pump or Replicat) is unable to process the data stream at a fast enough rate to keep up with the source system. The slower rate results in an increased latency between the source and destination databases. Oracle initially recommends to first configure a single process and monitor replication lag along with end-to-end performance before adding additional processes. For GoldenGate performance configuration guidelines refer to the MAA Oracle GoldenGate Performance Best Practices white paper: http://www.oracle.com/technetwork/database/availability/maa-gg-performance-1969630.pdf
If a single GoldenGate process is still not performing fast enough, performance may be increased by dividing the work between multiple processes. Be aware that if you create multiple Extract processes, you will also need to create separate Data Pump and Replicat process to transfer and apply each set of trail files. Similarly, if you create multiple Data Pump processes, additional Replicats will be required.
The task of dividing work between GoldenGate processes can be a time consuming manual process using the process report files or logdump output. As an alternative, the Perl code presented in this note will take a GoldenGate report file or logdump output file and automatically divide the work between a number of processes.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms