Fatal Ni Connect Error 12538
Contents |
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB fatal ni connect error 12170 tns-12535 Don Burleson Blog
fatal ni connect error 12170 firewall ORA-12538: TNS: no such protocol adapter Oracle Database Tips by Burleson Consulting From the OracleFatal Ni Connect Error 12170 Ora-3136
documentation we see this on the ORA-12538 error: ORA-12538: TNS:no such protocol adapter Cause: The protocol adapter requested (by way of the '(PROTOCOL=..)'; keyword-value pair in a TNS address) is
Ns Main Err Code: 12535
unknown. If the supplied address is typographically correct then the protocol adapter is not installed. Action: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA). Solutions: If TNS_ADMIN is set then you should be able to use fatal ni connect error 12637 a network alias, not the full "(DESCRIPTION..." connect string. The TNS_ADMIN parm tells Oracle clients where to find the tnsnames.ora file. Setting the ORACLE_HOME environment variable incorrectly on a Windows based system will create this problem. �� Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum. Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications. Errata? Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback. Just e-mail: and include the URL for the page. Burleson Consulting The
+ Solutions etc. Wednesday, August 20, 2014 Removing Fatal NI connect error 12170 from Database Alert Log In our one of the 11gR2 Production Database, there were so many entries w.r.tFatal NI connect error
Oracle 12c Fatal Ni Connect Error 12170
12170 + TNS-12535: TNS:operation timed out +TNS-00505: Operation timed out (with different ports), nt secondary err code: 110 found in both RAC Instances Alert Log file. Problem: Fatal NI connect error 12170. VERSION INFORMATION: tns-00505: operation timed out 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 http://www.dba-oracle.com/t_iora_12538_tns_no_protocol_adapter.htm 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 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 http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html 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. Because it sends packets to application servers every ten minutes, the connections are detected as active by firewalls and they are not broken. **In an installation that includes GRID, this parameter should be set in the RDBMS_HOME/network/admin/sqlnet.ora file. This would be the default location for sqlnet.ora file parameters referenced by the instance. 2) One w
some more feedback. In my alert log, I constantly receive this error: Fatal NI connect error 12170. VERSION http://www.cornbio.com/oracle-fatal-ni-connect-error-12170-issue/ INFORMATION: TNS for 64-bit Windows: Version 11.1.0.6.0 - Production Read more 2013-11-27 09:36 Oracle Fatal NI connect error 12170 - with ns secondary err code: 12606 on a Windows server 2003 R2 SP2, the Oracle database (10.2.0.2) and listener are both running and I can connect through the listener to the database on the databaseserver. Coming from fatal ni another server (cilentside), the cilent gets time-out (ora-)error, Read more 2014-01-26 15:37 Oracle Fatal NI connect error 12170 - time out Got quite a few these error in alert.log file from an Oracle 11g2 Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - fatal ni connect Production TCP/IP Read more 2015-03-16 11:13 Oracle Fatal NI connect error 12170. Message: Listener response to a TNS ping is 450 msecs When i checked in sqlnet.log file i found this error. We dont have sqlnet.ora file. Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 10.2.0.4.0 - Production Oracle Bequeat Read more 2015-05-30 00:41 Oracle Fatal NI connect error 12170 with - nt main err code: 505 i've got a Linux database Red Hat ES4 and an Oracle 10.2.0.2 (both 32bit), everythings works fine, only there is in de listenerlog directory a sqlnet.log file that keeps growing, in the file is the following: Fatal NI connect error 12170. VERSION INF Read more 2012-04-15 07:50 Oracle Fatal NI connect error 12170 and TNS-12535: TNS:operation timed out We are getting intermittently following error. TNS for Solaris: Version 10.2.0.3.0 - Production Oracle Bequeath NT Protocol Adapter for Solaris: Version 10.2.0.3.0 - Production TCP/IP NT Protocol Adapter for Solaris: Version 10.2.0.3.0 - Production T Read more 2013-05-20 06:49 Oracle Question about 'Fatal