3 Replies Latest reply: Oct 3, 2013 12:35 PM by Eduardo Legatti Branched from an earlier discussion. RSS

    Re: Fatal NI connect error 12170.

    bjb24

      I had a similiar issue today in my 11.2 RAC database alert.log.

       

      Found MOS doc

        • 1. Re: Fatal NI connect error 12170.
          sb92075

          bjb24 wrote:

           

          I had a similiar issue today in my 11.2 RAC database alert.log.

           

          Found MOS doc

          how can we reproduce what you report?

          • 2. Re: Fatal NI connect error 12170.
            bjb24

            Reproducing a timeout issue can be tricky. Often, they occur around the same time and are caused by heavy network traffic. You could re-create the issue by flooding your network or your NICs and try to connect. A lot of applications and app servers will retry the connection and it will be successful. I believe that is why there is another MOS doc that explains how you can remove these informational messages from your alert.log. I wouldn't recommend doing that though.

             

            Do you really want do know how to reproduce this? Or, are you asking me to show proof?

            • 3. Re: Fatal NI connect error 12170.
              Eduardo Legatti

              Hi,

               

              Currently, I'm having these kind of problems in some databases in my developer environment.. I spent some time investigating, but I didn't find a solution yet. I read many documents(MOS), and try other things...

               

              Fatal NI connect error 12537, connecting to:

              (LOCAL=NO)

               

                VERSION INFORMATION:

              TNS for Linux: Version 11.2.0.3.0 - Production

              Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production

              TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production

                Time: 18-SEP-2013 22:20:03

                Tracing not turned on.

                Tns error struct:

                  ns main err code: 12537

               

              TNS-12537: TNS:connection closed

                  ns secondary err code: 12560

                  nt main err code: 0

                  nt secondary err code: 0

                  nt OS err code: 0

              opiodr aborting process unknown ospid (6536) as a result of ORA-609

               

               

              The only thing that I notice that these errors star to raise after maintenance plan window at 22:00 PM

               

              2013-09-18 22:00:00.253000 -03:00

              Setting Resource Manager plan SCHEDULER[0x3109]:DEFAULT_MAINTENANCE_PLAN via scheduler window

              Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter

              Starting background process VKRM

               

              Cheers

               

              Legatti