Oracle Fatal Ni Connect Error 12170
Contents |
+ Solutions etc. Wednesday, August 20, 2014 Removing Fatal NI connect error 12170 from Database Alert Log In our one of the fatal ni connect error 12170 ora-3136 11gR2 Production Database, there were so many entries w.r.tFatal NI connect fatal ni connect error 12170 firewall error 12170 + TNS-12535: TNS:operation timed out +TNS-00505: Operation timed out (with different ports), found in both ns main err code: 12535 RAC Instances Alert Log file. Problem: Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.3.0 - Production fatal ni connect error 12170 oracle 12c 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: 20-AUG-2014 14:17:36 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary
Fatal Ni Connect Error 12637
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=xxx.xxx.xxx.xxx)(PORT=44326)) Reason: The same error message was repeating during whole day almost for every application server.I've finally found what was causing the problem. Our database is behind a firewall. Firewall has an "idle session timeout" value. If a connection remains idle for more than the "idle session timeout" value it drops the connections.Application developers usually configure their connection pools to remain alive for a long time, which is more than the "idle session timeout" value of the firewall. Not all the connections in the pool are used. Some stays idle. After sometime the firewall drops them and I get those operation timed out problems. Solution / Workaround: 1) Add the following line to the sqlnet.ora file on the server. SQLNET.EXPIRE_TIME=10In this configuration database will probe the application servers every 10 minutes to se
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
Nt Secondary Err Code: 110
to: (LOCAL=NO) VERSION INFORMATION: TNS for 64-bit Windows: Version 11.2.0.3.0 - Production Oracle fatal ni connect error 12170 tns-12535 12606 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: fatal ni connect error 12170 sap Version 11.2.0.3.0 - Production Time: 23-JUL-2014 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 http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html err code: 0 nt OS err code: 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: 63911Registered: March 2007 Location: Nanterre, France, http://... Senior MemberAccount Moderator ORA-12547: TNS:lost contact *Cause: Partner has unexpectedly gone http://www.orafaq.com/forum/t/193730/ away, usually during process startup. *Action: Investigate partner application for abnormal 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: 63911Registered: March 2007 Location: Nanterre, France, http://... Senior Memb
this Document Symptoms Changes Cause Solution References APPLIES TO: Oracle Net Services - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1] Information http://dbafoiz.blogspot.com/2015/03/12170-tns-12535tns-00505-operation.html in this document applies to any platform. SYMPTOMS The following error http://dbaforums.org/oracle/index.php?showtopic=21776 is reported in the database alert log. ***Note the "Client address" is posted within the error stack in this case. 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 fatal ni 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: 22-FEB-2014 12:45:09 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: 60 nt OS fatal ni connect err code: 0 ***Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=121.23.142.141)(PORT=45679)) The PORT field here is the ephemeral port assigned to the client for this connection. This does not correspond to the listener port. CHANGES No changes are necessary, but may have recently upgraded the database to 11g release 1 or higher, or installed a new Oracle11g database and they are now visible in the alert log. Note: Prior to 11gR1 these same 'Fatal NI connect error 12170' are written to the sqlnet.log. This document describes a problem that arises when a firewall exists between the client and the database server. CAUSE We can search the listener log covering the same time period using this search criteria. (HOST=121.23.142.141)(PORT=45679) The 11glistener log in text format is located here: $ORACLE_BASE/diag/tnslsnr///trace/.log Again, this is the client's IP address and the unique ephemeral port assigned to the client for this connection. In this case, we findthat this connection was established at the listener at this timestamp: 22-FEB-2014 10:42:10* (CONNECT_DATA=(SID=test)(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))) * (ADDRESS=(PROTOCOL=tcp)(HOST=121.23.142.141)(PORT=45679))* establish