Fatal Ni Connect Error
Contents |
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting
Fatal Ni Connect Error 12170 Ora-3136
PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB fatal ni connect error 12170 firewall Don Burleson Blog
ns main err code: 12535 fatal ni connect error 12170 Oracle Database Tips by Burleson Consulting November 5, 2015 Question: Below error getting in alert log file every day, butFatal Ni Connect Error 12637
database is working fineWhat are the reason for this Fatal ni connect error 12170? Fatal NI connect error 12170. VERSION INFORMATION: TNS for 64-bit Windows: Version 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows:
Oracle 12c Fatal Ni Connect Error 12170
Version 11.2.0.1.0 - Production Time: 28-MAY-2012 19:20:02 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 Answer: The fatal ni connect error 12170 is related to the ORA-12170 error: ORA-12170: TNS:Connect timeout occurredCause: The client failed to establish a connection and complete authentication in the time specified by the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in the sqlnet.ora file. This error may be a result of network or system delays, or it may indicate that a malicious client is trying to cause a denial-of-service attack on the database server. The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.Action:
Fatal NI connect error 12547 [message #619535] Wed, 23 July 2014 04:30 Subbu19 Messages: 15Registered: July 2014 Location: Chennai Junior Member Hi, Following message occurs on alert.log file Fatal NI connect error 12547, connecting to: (LOCAL=NO) VERSION INFORMATION: nt secondary err code: 110 TNS for 64-bit Windows: Version 11.2.0.3.0 - Production Oracle Bequeath NT Protocol Adapter for
Fatal Ni Connect Error 12170 Sap
64-bit Windows: Version 11.2.0.3.0 - Production Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production Time: 23-JUL-2014 fatal ni connect error 12638 04:18:15 Tracing not turned on. Tns error struct: ns main err code: 12547 TNS-12547: TNS:lost contact ns secondary err code: 12560 nt main err code: 0 nt secondary err code: 0 nt OS err code: http://www.dba-oracle.com/t_fatal_ni_connect_error_12170.htm 0 opiodr aborting process unknown ospid (12900) as a result of ORA-609 Report message to a moderator Re: Fatal NI connect error 12547 [message #619544 is a reply to message #619535] Wed, 23 July 2014 05:11 Michel Cadot Messages: 63883Registered: March 2007 Location: Nanterre, France, http://... Senior MemberAccount Moderator ORA-12547: TNS:lost contact *Cause: Partner has unexpectedly gone away, usually during process startup. *Action: Investigate partner application for abnormal http://www.orafaq.com/forum/t/193730/ termination. On an Interchange, this can happen if the machine is overloaded. Report message to a moderator Re: Fatal NI connect error 12547 [message #619548 is a reply to message #619544] Wed, 23 July 2014 05:53 Subbu19 Messages: 15Registered: July 2014 Location: Chennai Junior Member Hi Michel, Now i am getting a different error code from alert.log file Fatal NI connect error 12170. VERSION INFORMATION: TNS for 64-bit Windows: Version 11.2.0.3.0 - Production Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production Time: 23-JUL-2014 05:24:17 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=10.122.161.90)(PORT=50611)) WARNING: inbound connection timed out (ORA-3136) Report message to a moderator Re: Fatal NI connect error 12547 [message #619556 is a reply to message #619548] Wed, 23 July 2014 06:43 Michel Cadot Messages: 63883Registered: March 2007 Location: Nanterre, France, http://... Senior MemberAccount Moderator ORA-12535: TNS:operation timed out *Cause: The requested operation could not be completed within the time out period. *Action: Look at the documentatio
have a script to monitor the alert.log file for any ORA-xxxx errors. With https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ 11g we found out many entries in regards of: Fatal http://www.vmcd.org/2011/12/problem-fatal-ni-connect-error-12170-tns-12535-tnsoperation-timed-out-reported-in-11g-alert-log/ NI connect error The problem: alert.log file has many entries for Fatal NI connect error. Examples: *********************************************************************** Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=nnn))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=sss)(CID=(PROGRAM=oracle)(HOST=xxx)(USER=oracle)))) VERSION INFORMATION: TNS for Linux: Version 11.2.0.2.0 - Production TCP/IP NT Protocol Adapter for fatal ni Linux: Version 11.2.0.2.0 - Production Time: 17-JAN-2011 10:20:45 Tracing not turned on. Tns error struct: ns main err code: 12564 TNS-12564: TNS:connection refused ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Error 12514 received logging on to the fatal ni connect standby Mon Jan 17 10:21:45 2011 *********************************************************************** or *********************************************************************** 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: 18-JAN-2011 15:13:08 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 nt main err code: 505 TNS-00505: Operation timed out nt secondary err code: 110 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=xx.xx.x.xx)(PORT=nnnn)) Tue Jan 18 15:40:20 2011 The solution: We will have an entry on the alert.log file every time a client connection of any kind fails to complete or is aborted. One way to minimize the impact is by using the parameter SQLNET.INBOUND_CONNECT_TIMEOUT (default to 60 seconds on 10gR2 and 11g) but, sometimes, this value is not adequate. Or
network, oracle Applies to: Oracle Net Services - Version: 11.1.0.6 to 11.2.0.2 - Release: 11.1 to 11.2 Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.2.0.2 [Release: 11.1 to 11.2] Information in this document applies to any platform. TNS-12170, ORA-12170, TNS-12535, TNS-00505 alert.log Symptoms nt secondary err code: 110 Monitoring of the 11g database Alert log(s) may show frequent timeout related messages such as: - On Oracle Solaris: *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for Solaris: Version 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.1.0 - Production TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.1.0 - Production Time: 22-JAN-2011 21:48:23 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 nt main err code: 505 TNS-00505: Operation timed out nt secondary err code: 145 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.159.34.117)(PORT=1092)) ------ The "nt secondary err code" will be different based on the operating system. Linux x86 or Linux x86-64: "nt secondary err code: 110" HP-UX Server: "nt secondary err code: 238" AIX: "nt secondary err code: 78" Changes No change are necessary, but may have recently upgraded the database to 11g release 1 or higher, or installed a new Oracle11g database. Note: Prior to 11gR1 these same ‘Fatal NI connect error 12170' are written to the sqlnet.log Cause These time out related messages are mostly informational in nature. The messages indicate the specified client connection (identified by the ‘Client address:' details) has experienced a time out. The ‘nt secondary err code' identifies the underlying network transport, such as (TCP/IP) timeout limits after a client has abnormally terminated the database connection. The ‘nt secondary err code' translates to underlying network transport timeouts for the following Operating Systems: For the Solaris system: nt secondary err code: 145: ETIMEDOUT 145 /* Connection timed out */ For the Linux operating system: nt secondary err code: 110 ETIMEDOUT 110 Connection timed out For the HP-UX system: nt secondary err code: 238: ETIMEDOUT 238 /* Connection ti