5 Replies Latest reply: Jul 25, 2011 1:24 AM by 876431 RSS

    TCP/IP error 111 (Connection refused).?

    user2017273
      Hi,

      I have configured replication using Golden gate. After starting extract .. i am getting following follwing error.

      How to resolve this error. please help me


      Error:

      GGS WARNING 150 Oracle GoldenGate Capture for Oracle, ext1.prm: TCP/IP error 111 (Connection refused)
        • 1. Re: TCP/IP error 111 (Connection refused).?
          MikeN
          user2017273 wrote:

          I have configured replication using Golden gate. After starting extract .. i am getting following follwing error.
          How to resolve this error. please help me
          Error:

          GGS WARNING 150 Oracle GoldenGate Capture for Oracle, ext1.prm: TCP/IP error 111 (Connection refused)
          What is the contents of the report file?? (note that the report file also has the contents of the paramter file... a double benefit for us so that we can better guess what the issue is...)
          ggsci> view report ext1
          ...details?
          The problem is, most likely, that you have your extract "ext1" writing to a remote trail (RmtHost {hostname}, mgrPort 7801), and the remote manager is either not running, or is not running on the correct/expected port (in this example, 7801). Also be sure "ext1.prm" uses the correct syntax for specifying the rmthost: it's "mgrport", not just "port".

          Good luck,
          -Michael
          • 2. Re: TCP/IP error 111 (Connection refused).?
            user2017273
            Hi,

            Now i am getting different error

            Log file:

            GGSCI (test1.domain.com) 28> view report ext1


            ***********************************************************************
            Oracle GoldenGate Capture for Oracle
            Version 10.4.0.19 Build 002
            Linux, x86, 32bit (optimized), Oracle 10 on Sep 18 2009 00:01:59

            Copyright (C) 1995, 2009, Oracle and/or its affiliates. All rights reserved.


            Starting at 2011-07-21 08:02:03
            ***********************************************************************

            Operating System Version:
            Linux
            Version #1 Wed Jan 5 19:22:18 EST 2005, Release 2.6.9-5.EL
            Node: test1.domain.com
            Machine: i686
            soft limit hard limit
            Address Space Size : unlimited unlimited
            Heap Size : unlimited unlimited
            File Size : unlimited unlimited
            CPU Time : unlimited unlimited

            Process id: 3601

            Description:

            ***********************************************************************
            ** Running with the following parameters **
            ***********************************************************************
            extract ext1
            userid ggs_owner, password *********
            rmthost 192.168.0.108, mgrport 7809
            rmttrail /u01/gg/dirdat/lt
            ddl include mapped objname scott.*;
            table scott.*;


            CACHEMGR virtual memory values (may have been adjusted)
            CACHEBUFFERSIZE: 64K
            CACHESIZE: 2G
            CACHEBUFFERSIZE (soft max): 4M
            CACHEPAGEOUTSIZE (normal): 4M
            PROCESS VM AVAIL FROM OS (min): 2.92G
            CACHESIZEMAX (strict force to disk): 2.68G

            Database Version:
            Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Prod
            PL/SQL Release 10.2.0.5.0 - Production
            CORE 10.2.0.5.0 Production
            TNS for Linux: Version 10.2.0.5.0 - Production
            NLSRTL Version 10.2.0.5.0 - Production

            Database Language and Character Set:
            NLS_LANG = "AMERICAN_AMERICA.US7ASCII"
            NLS_LANGUAGE = "AMERICAN"
            NLS_TERRITORY = "AMERICA"
            NLS_CHARACTERSET = "US7ASCII"

            2011-07-21 08:02:08 GGS INFO 406 Socket buffer size set to 27985 (flush size 27985).

            2011-07-21 08:02:18 GGS INFO 112 No recovery is required for target file /u01/gg/dirdat/lt000000, at RBA 0 (file not opened).

            2011-07-21 08:02:18 GGS INFO Z0-05M Output file /u01/gg/dirdat/lt is using format RELEASE 10.4.

            Source Context :
            SourceModule : [er.extrout]
            SourceID : [$Id: //depot/releases/OpenSys/v10.4.0/src/app/er/extrout.c#4 $]
            SourceFunction : [complete_tcp_msg]
            SourceLine : [1342]
            ThreadBacktrace : [8] elements
            : [u01/gg/extract(_ZN15CMessageContext16AddThreadContextEv+0x26) [0x825bb56]]
            : [u01/gg/extract(_ZN15CMessageFactory13CreateMessageEP14CSourceContextjz+0x533) [0x824fc43]]
            : [u01/gg/extract(_Z16complete_tcp_msgP11extract_def+0x7d7) [0x80c3347]]
            : [u01/gg/extract [0x80ce7b1]]
            : [u01/gg/extract(_Z19open_targ_ext_filess+0xa5) [0x80c2525]]
            : [u01/gg/extract(main+0x6d0) [0x80ff900]]
            : [lib/tls/libc.so.6(__libc_start_main+0xe3) [0xc0ee33]]
            : [u01/gg/extract [0x809b5e1]]

            *2011-07-21 08:02:18 GGS ERROR 112 There is a problem in network communication, a remote file problem, encryption keys for target and source do not ma*
            tch (if using ENCRYPT) or an unknown error. (Remote file used is /u01/gg/dirdat/lt000000, reply received is Could not create /u01/gg/dirdat/lt000000).

            *2011-07-21 08:02:18 GGS ERROR 190 PROCESS ABENDING.*
            • 3. Re: TCP/IP error 111 (Connection refused).?
              stevencallan
              Does your GG user have rw permissions for the directory you are using?
              • 4. Re: TCP/IP error 111 (Connection refused).?
                844166
                Dear you have two different problems...

                On your first problem you should check the target server port opend or not for sorce server. TCP/IP connection (port) must established for this communication. You can check this by using telnet to target server from source server.

                Now on your second question...

                If everything is working fine for port connectivity, and no issue. You check that whether already file is created for the same name. You can also check whether same name file is created over the target location. You can check the goldengate authentication on that perticular server mount.
                • 5. Re: TCP/IP error 111 (Connection refused).?
                  876431
                  Hi,

                  Error:
                  GGS WARNING 150 Oracle GoldenGate Capture for Oracle, ext1.prm: TCP/IP error 111 (Connection refused)

                  Explanation:
                  "Connection refused" indicates one of the following:
                  No application running on the remote system is listening to the specified port
                  The MGR process is not running
                  The "static" Server/Collector process is not running.
                  The "dynamic" Server/Collector process was slow to start (Extract should recover by retrying the connection).
                  The "dynamic" Server/Collector process failed to start.
                  The "dynamic" Server/Collector process terminated immediately after starting.
                  The application running on the remote system is listening to the specified port, but the connection request queue is full
                  Too many processes are opening connections to the specified port at the same time.
                  Extract is trying to connect to a Server/Collector port that already has an established connection.
                  Sometimes, firewalls refuse unauthorized connection requests.


                  Oracle GoldenGate Extract opens TCP/IP connections for two purposes:

                  To Send "START" requests to a remote MGR process.
                  To Send trail data to a remote Server/Collector process.

                  Extract may connect to a remote MGR to request that it start a "dynamic" Server/Collector process, in which case the MGR responds with the port number it assigned to the process it started, or Extract may connect directly to a "static" Server/Collector process.

                  In general, it is recommended using Dynamic Server/Collector processes.


                  Troubleshooting the MGR process on the remote system
                  ----------------------------------------------------------------------------------------------
                  Ensure that MGR is running on the remote system:

                  GGSCI (remote_system) 1> info mgr

                  Manager is running (IP port sysname.7890).

                  If not running, start mgr:

                  GGSCI (remote_system) 3> start mgr

                  Manager started.


                  If running, check that MGR is responding to connection requests and commands:

                  GGSCI (remote_system) 4> send mgr getportinfo detail

                  Sending GETPORTINFO, request to MANAGER ...

                  Entry Port Error Process Assigned Program
                  ----- ----- ----- ---------- ------------------- -------
                  0 7891 0
                  1 7892 0
                  2 7893 0
                  3 7894 0
                  4 7895 0

                  If the comnand times out, kill and restart MGR:

                  $ ps -f | grep ./mgr
                  gguser 782474 1171604 0 12:46:30 pts/2 0:04 ./mgr mgr PARAMFILE /home/gguser/v10.4.0.19/dirprm/mgr.prm REPORTFILE /home/gguser/v10.4.0.19dirrpt/MGR.rpt PROCESSID MGR PORT 7809 > /home/gguser/v10.4.0.19/dirout/MGR.out
                  $ kill -9 782474
                  $ ggsci

                  GGSCI > start mgr

                  Manager started.


                  Troubleshooting MGR connection problems from the local system
                  -------------------------------------------------------------------------------------------------------------------
                  After ensuring that MGR is running and responsive on the remote system, check whether a connection can be established.

                  Using the wrong port number, or when a firewall refuses a connection attempt:

                  $ telnet remote_system_name 7809

                  Trying...
                  telnet: connect: A remote host refused an attempted connect operation.

                  Using the correct port number:
                  $ telnet remote_system_name 7890

                  Trying...
                  Connected to axe01.
                  Escape character is '^]'.

                  ^]

                  telnet> close
                  Connection closed.

                  Troubleshooting Server/Collector connection problems
                  ------------------------------------------------------------------------------------------
                  Look for messages related to starting dynamic Server/Collector processes in ggserr.log on the remote system.

                  2009-05-18 13:56:43 GGS INFO 301 GoldenGate Manager for DB2, mgr.prm: Command received from EXTRACT on host 192.168.118.59 (START SERVER CPU -1 PRI -1 PARAMS -c ON).
                  2009-05-18 13:56:43 GGS INFO 302 GoldenGate Manager for DB2, mgr.prm: Manager started collector process (Port 7891).
                  2009-05-18 13:56:43 GGS INFO 373 GoldenGate Collector, port 7891: Waiting for connection (started dynamically).

                  If the Server/Collector process (either static or dynamic) is running, but Extract cannot establish a connection, you may attempt to connect to the Server/Collector process using the "telnet" client utility program:

                  $ telnet remote_server_name 7891

                  Trying...
                  telnet: connect: A remote host refused an attempted connect operation.

                  The above indicates that either the Server/Collector process is not listening to the specified port, or a firewall is refusing the connection request. The "Connection refused" message may be slightly different on different systems, for example:

                  Trying 192.168.168.192...
                  telnet: connect to address 192.168.168.192: Connection refused
                  telnet: Unable to connect to remote host

                  Successful connections using telnet indicate that the routing is correct and any network firewalls are allowing connections through:

                  $ telnet remote_system_name 7890

                  Trying...
                  Connected to system_name.
                  Escape character is '^]'.

                  ^]

                  telnet> close
                  Connection closed.

                  Note that the Server/Collector process will terminate when the connection is closed.

                  Even though telnet may be able to establish a connection, there may still be problems with system software that monitors application activity and blocks connections from unauthorized applications - for example, if "telnet" is "authorized", and "extract" is not, "telnet" can establish connections, but "extract" will be unable to connect:. Whether extract gets "Connection refused" or "Connection timeout" or a different error depends on the software that blocks connections from "unauthorized" programs.

                  Routing problems and firewalls that drop unauthorized packets may cause a connection timeout:

                  $ telnet 192.168.168.192 12345
                  Trying...
                  telnet: connect: A remote host did not respond within the timeout period.

                  To check for routing problems, use traceroute, a program that traces the path packets take through the network by setting the "Time-To-Live" (TTL) value to cause the routers along the way to return the "expired" packets; each router that receives the packet decrements the TTL and when it hits zero, that router returns the packet; the traceroute program then displays the "hop count" (TTL value), the address(es) of the router(s) that returned the packet, and the time it took to receive responses from three packets. Timeouts are indicated by an "*" instead of the response time.

                  If the above didn't help identify the problem, contact your network administrator to check firewall settings.


                  Thanks & Regards
                  SK