Goldengate 源端 dump進程無法啓動報;scoket buffer size set to xxx connect failed to targetIP:7819,error

一；問題現象；

Goldengate 源端 dump進程無法啓動報;

scoket buffer size set to 5000000 (flush size

connect failed to targetIP:7819,error

二；環境描述

環境爲目標端和源端爲異地，兩邊都有firewall。

mgr開放端口並不是7819

在這個情況下對端口的要求如下；

Oracle® GoldenGate

Windows and UNIX Administrator’s Guide 

0. Maintaining ports for remote connections through firewalls

   If a firewall is being used at an Oracle GoldenGate target location, additional ports are

   ..............................................................................Oracle GoldenGate Windows and UNIX Administrator’s Guide 20

required on the target system to receive dynamic TCP/IP communications from remoteOracle GoldenGate processes. These ports are:

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

• ●  One port for each Replicat process that is started by the local Manager as part of aremote task. A remote task is used for initial loads and is specified with the RMTTASKparameter. This port is used to receive incoming requests from the remote Extractprocess.

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

• ●  Ports for the other Oracle GoldenGate products if they interact with the local OracleGoldenGate 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.

  • ●  Each Manager instance on a system must use a different port list.

    Although not a required parameter, DYNAMICPORTLIST is strongly recommended for bestperformance. The Collector process is responsible for finding and binding to an availableport, and having a known list of qualified ports speeds this process. In the absence ofDYNAMICPORTLIST (or if not enough ports are specified with it), Collector tries to use port 7840for remote requests. If 7840 is not available, Collector increments by one until it finds anavailable port. This can delay the acceptance of the remote request. If Collector runs out ofports 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” on page 170.
    For more information about PORT and DYNAMICPORTLIST, see the Oracle GoldenGate Windows

    and UNIX Reference Guide. 

此類問題可以提過如下手段觀察到；

1. ping測試

2. telent target port

3. tcpdump -v host <SOURCE> and <TARGET> 

解決方法；

通過詢問發現客戶由於端口需要使用，將mgr的DYNAMICPORTLIST參數刪除，只使用了prot參數指定了1個端口導致。

提過重新更換其他端口並添加DYNAMICPORTLIST參數搞定。