10.3 Maintaining Ports for Remote Connections through Firewalls

If a firewall is being used at an Oracle GoldenGate target location, additional ports are required on the target system to receive dynamic TCP/IP communications from remote Oracle GoldenGate processes. These ports are:

  • One port for each Collector process that is started by the local Manager to receive propagated transaction data from remote online Extract processes. When an Extract process sends data to a target, the Manager on the target starts a dedicated Collector process.

  • One port for each Replicat process that is started by the local Manager as part of a remote task. A remote task is used for initial loads and is specified with the RMTTASK parameter. This port is used to receive incoming requests from the remote Extract process. See RMTTASK in Reference for Oracle GoldenGatefor more information.

  • Some extra ports in case they are needed for expansion of the local Oracle GoldenGate configuration.

  • Ports for the other Oracle GoldenGate products if they interact with the local Oracle GoldenGate instance, as stated in the documentation of those products.

To specify these ports, use the DYNAMICPORTLIST parameter in the Manager parameter file. Follow these guidelines:

  • You can specify up to 5000 ports in any combination of the following formats:

    7830, 7833, 7835
    7830-7835
    7830-7835, 7839
    
  • The ports must be unreserved and unrestricted.

  • If more than one instance of Oracle GoldenGate exists on the system, then each Manager must use a different port number.

Although not a required parameter, DYNAMICPORTLIST is strongly recommended for best performance. The Collector process is responsible for finding and binding to an available port, and having a known list of qualified ports speeds this process. In the absence of DYNAMICPORTLIST (or if not enough ports are specified with it), Collector can use a port range between 7819 and 12818. If Collector runs out of ports in the DYNAMICPORTLIST list, the following occurs:

  • Manager reports an error in its process report and in the Oracle GoldenGate ggserr log.

  • Collector retries based on the rules in the Oracle GoldenGate tcperrs file. For more information about the tcperrs file, see Handling TCP/IP Errors.

See DYNAMICPORTLIST in Reference for Oracle GoldenGate for more information.