Ports Used by Oracle GoldenGate

Oracle GoldenGate Manager is the controller process that instantiates the Oracle GoldenGate processes. Oracle GoldenGate manager requires opening ports for both the itself and the local processes. 

Found this picture on twitter. It's fun while intuitive way of explaining TCP/IP.  :-)

First, each Oracle GoldenGate manager process has to have a unique port. This port is used to communicate between the manager process and other Oracle GoldenGate processes. This is configured in the manager parameter file (mgr.prm) using the PORT parameter.

​Second, for Oracle GoldenGate local processes to bind with remote communications, there is a need for a range of ports. This range can start starting at port 7840 or a customized range of up to 5000 other ports (as of GoldenGate 12.2). This is configured with the DYNAMICPORTLIST parameter. The followings are the processes needs ports allocated by DYNAMICPORTLIST:

• Collector: to communicate with a remote Extract to receive incoming data.
• Replicat: to communicate with a remote Extract to receive data during an initial load task.
• Passive Extract: to communicate with a remote Collector
• ​GGSCI: to issue remote commands

The following is an example manager parameter file: ​

port 7809
DynamicPortList 7820-7830, 7833, 7835

Fully understand how GoldenGate uses and manages the ports will help you speed up the setup process especially in a cloud environment where opening ports is highly restricted.