11 Replies Latest reply: Jan 10, 2013 3:28 PM by 984199 Branched to a new discussion. RSS

    Fatal NI connect error 12170.

    user8039531
      I have Oracle DB 11.2 ON Linux Suse: In my alert log, I can see:

      Fatal NI connect error 12170.

      VERSION INFORMATION:
      TNS for Linux: Version 11.2.0.2.0 - Production
      Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
      TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
      Time: 21-AUG-2012 11:19:28
      Tracing not turned on.
      Tns error struct:
      ns main err code: 12535

      TNS-12535: TNS:operation timed out
      ns secondary err code: 12606
      nt main err code: 0
      nt secondary err code: 0
      nt OS err code: 0
      Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=11.125.190.132)(PORT=61658))
      WARNING: inbound connection timed out (ORA-3136)
        • 1. Re: Fatal NI connect error 12170.
          sb92075
          user8039531 wrote:
          I have Oracle DB 11.2 ON Linux Suse: In my alert log, I can see:

          Fatal NI connect error 12170.

          VERSION INFORMATION:
          TNS for Linux: Version 11.2.0.2.0 - Production
          Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
          TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
          Time: 21-AUG-2012 11:19:28
          Tracing not turned on.
          Tns error struct:
          ns main err code: 12535

          TNS-12535: TNS:operation timed out
          ns secondary err code: 12606
          nt main err code: 0
          nt secondary err code: 0
          nt OS err code: 0
          Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=11.125.190.132)(PORT=61658))
          WARNING: inbound connection timed out (ORA-3136)
          When was last time SQL*Net worked without any error?
          what changed since then?

          a common cause for timeout is FireWall on or between client & DB Server.
          • 2. Re: Fatal NI connect error 12170.
            sybrand_b
            1 Errors can be looked up in the online documentation PRIOR to asking a question.
            You just used copy and paste without doing any analysis, this is a violation of Forums Etiquette which recommends to consult documentation first
            2 Using hardcoded IP addresses is a big no no, as it will make your 'system' maintenance prone
            3 12170 in conjunction with 12535 means one thing: firewall
            There are standard solutions for that, they are documented, and I have posted them here many times, so I'm not going to repeat them.

            ------------
            Sybrand Bakker
            Senior Oracle DBA
            • 3. Re: Fatal NI connect error 12170.
              user8039531
              Thanks

              What Do you Think about:

              NET.ORA:
              SQLNET.INBOUND_CONNECT_TIMEOUT = 120

              LISTENER.ORA:
              INBOUND_CONNECT_TIMEOUT_<listener name> = 120

              Is possible apply this changes? or is a network problem?

              Regards,

              Guido
              • 4. Re: Fatal NI connect error 12170.
                sybrand_b
                These questions are irrelevant.

                Problem is caused by firewall, as I already explained, and you didn't bother to read.

                Your approach is going to fix zero, nada, niente, nothing.

                ---------
                Sybrand Bakker
                Senior Oracle DBA
                • 5. Re: Fatal NI connect error 12170.
                  sb92075
                  Handle:     user8039531
                  Status Level:     Newbie
                  Registered:     May 23, 2012
                  Total Posts:     76
                  Total Questions:     19 (18 unresolved)

                  why do you waste time here when you rarely get answer to your questions?
                  • 6. Re: Fatal NI connect error 12170.
                    user8039531
                    Thanks for all. Regards,
                    • 7. Re: Fatal NI connect error 12170.
                      jr*323216*an
                      "2 Using hardcoded IP addresses is a big no no, as it will make your 'system' maintenance prone"

                      true in general, at least as it applies to servers, but in this case the log pretty clearly shows a client ip
                      Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=11.125.190.132)(PORT=61658))
                      • 8. Re: Fatal NI connect error 12170.
                        user12097081
                        Dear Sybrand,

                        I have installed Oracle 11g Release 2 Cluster Database and using DNS for SCAN connectivity. I am unable to connect from 10.2.0.4 client. The connection hangs indefinitely and then times out with the error "ORA-12170: TNS:Connect timeout occurred". Sqlnet.log recorded "Fatal NI connect error 12170".

                        I have an environment where firewalls are used. As you say, if this is a firewall issue, then how to workaround it?

                        Thanks
                        Shahid.
                        • 9. Re: Fatal NI connect error 12170.
                          sb92075
                          user12097081 wrote:

                          I have an environment where firewalls are used. As you say, if this is a firewall issue, then how to workaround it?
                          shutdown, turn off & disable Firewall to confirm it is source.
                          • 10. Re: Fatal NI connect error 12170.
                            Gerrit Haase
                            The pride of some people calling themselves "senior" is outstanding ;)
                            • 11. Re: Fatal NI connect error 12170.
                              984199
                              Sybrand always has a chip on his shoulder. I think it makes him happy to chew people out on this board for failure to follow protocol.