Fatal Ni Connect Error 12170 Linux
Contents |
+ Solutions etc. Wednesday, August 20, 2014 Removing Fatal NI connect error 12170 from Database Alert Log In our one of the 11gR2 Production Database, fatal ni connect error 12170 firewall there were so many entries w.r.tFatal NI connect error 12170 +
Fatal Ni Connect Error 12170 Ora-3136
TNS-12535: TNS:operation timed out +TNS-00505: Operation timed out (with different ports), found in both RAC Instances Alert Log ns main err code: 12535 file. Problem: Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.3.0 - Production Oracle Bequeath NT fatal ni connect error 12637 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 err code: 12560 nt main err
Oracle 12c Fatal Ni Connect Error 12170
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 see if they are up. In fact this is a mechanism to determine stale connections by database.
[message #647784] Mon, 08 February 2016 01:14 ashishkumarmahanta80 Messages: 231Registered: October 2006 Location: kolkatta Senior Member Dear All, Now a days, nt secondary err code: 110 I am getting below error at production database's alert. Please tns-00505: operation timed out let me know, whether it is purely related to networking issue? Though, In awr report, it come
Fatal Ni Connect Error 12638
at last Top 10 Foreground Events by Total Wait Time. Mon Feb 08 12:40:03 2016 Thread 1 cannot allocate new log, sequence 67751 Checkpoint not complete Current http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html log# 2 seq# 67750 mem# 0: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo02a.log Current log# 2 seq# 67750 mem# 1: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo02b.log Mon Feb 08 12:40:08 2016 *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.4.0 - Production Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - http://www.orafaq.com/forum/t/199962/ Production Time: 08-FEB-2016 12:40: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=192.168.16.102)(PORT=63557)) Mon Feb 08 12:40:14 2016 Thread 1 advanced to log sequence 67751 (LGWR switch) Current log# 5 seq# 67751 mem# 0: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05a.log Current log# 5 seq# 67751 mem# 1: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05b.log Mon Feb 08 12:40:14 2016 Archived Log entry 68360 added for thread 1 sequence 67750 ID 0xf94a7787 dest 1: Thread 1 cannot allocate new log, sequence 67752 Checkpoint not complete Current log# 5 seq# 67751 mem# 0: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05a.log Current log# 5 seq# 67751 mem# 1: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05b.log Waiting for your valuable inputs... Regards, Ashish Kumar Mahanta Report message to a moderator Re: Fatal NI connect error [message #647785 is a reply to message #647784] Mon, 08 February 2016 01:34 John Watson Messages: 6450Regis
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 - http://www.vmcd.org/2011/12/problem-fatal-ni-connect-error-12170-tns-12535-tnsoperation-timed-out-reported-in-11g-alert-log/ 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 http://www.redstk.com/oracle-tns-12535-and-dead-connection-detection/ 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 fatal ni 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: fatal ni connect 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
Services Services Managed Services Professional Services Enterprise Services License solutions Middleware Services Services Platform Services Hosting Cloud Advisory Service Proof of Concepts Project Management Services MANAGED SERVICE Business Transformation Business Transformation Business Analytics Cloud Solutions BigData & NoSQL Solutions BT 2 Development Services Technology Services BT 3 Engineered Systems Engineered Systems Patching Proof of Concept Systems Health Check E2 Migration Factory Workshops & Case Studies As a Service E3 Resources Case Studies News Events Whitepapers Podcasts Videos / Webinars Blog My Blog home blog Oracle Database Oracle TNS-12535 and Dead Connectio ... Oracle TNS-12535 and Dead Connection Detection by Svetoslav Gyurov on 31st March 2016 No comments These days everything goes to the cloud or it has been collocated somewhere in a shared infrastructure. In this post I'll talk about sessions being disconnected from your databases, firewalls and dead connection detection. Changes We moved number of 11g databases from one data centre to another. Symptoms Now probably many of you have seen the following error in your database alertlog "TNS-12535: TNS:operation timed out" or if you haven't you will definitely see it some day. Consider the following error from database alert log: Fatal NI connect error 12170. 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: 12-MAR-2015 10:28: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=192.168.0.10)(PORT=49831)) Thu Mar 12 10:28:09 2015 Now this error indicate timing issues between the server and the client. It's important to mention that those errors are RESULTANT, they are informational and not the actual cause of the disconnect. Although this error might happen for number of reasons it is commonly associated with firewalls or slow networks. Troubleshooting The best way to understand what's happening is to build a histogram of the duration of the sessions. In particular we want to understand whether disconnects are sporadic and random or they follow a