Fatal Ni Connect Error 12170 Alert Log
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, there were so many entries w.r.tFatal NI connect fatal ni connect error 12170 ora-3136 error 12170 + TNS-12535: TNS:operation timed out +TNS-00505: Operation timed out (with different
Fatal Ni Connect Error 12170 Firewall
ports), found in both RAC Instances Alert Log file. Problem: Fatal NI connect error 12170. VERSION INFORMATION: ns main err code: 12535 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 fatal ni connect error 12637 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 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))
Oracle 12c Fatal Ni Connect Error 12170
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. 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
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter nt secondary err code: 110 a title. You can not post a blank message. Please type your fatal ni connect error 12170 sap message and try again. More discussions in General Database Discussions All PlacesDatabaseGeneral Database Discussions This discussion is archived
Fatal Ni Connect Error 12638
6 Replies Latest reply on Dec 27, 2013 9:00 AM by adi_071 Fatal NI connect error 12547/12170 adi_071 Dec 19, 2013 2:17 PM Hi,I am stakk with connection problem on http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html customer Oracle server. Oracle database is installed on Microsoft Windows Server 2012 Standard. Version of Oracle DB is 11.2.0.4 Standard One Edition.Oracle database works fine on server. I had no problems/errors while installing (as admin). My user is memer of Local Admin Group. I am also able to connect to it with sqlplus (sqlplus username/password@tns_alias) and SQL Developer.Content of tnsnames, listener https://community.oracle.com/thread/2614609 og sqlnet files are following:tnsnames.oraORACLR_CONNECTION_DATA = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) ) (CONNECT_DATA = (SID = CLRExtProc) (PRESENTATION = RO) ) )SALES = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.9)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sales.company.se)))listener.oraSID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = CLRExtProc) (ORACLE_HOME = D:\oracle\product\11.2.0\dbhome_1) (PROGRAM = extproc) (ENVS = "EXTPROC_DLLS=ONLY:D:\oracle\product\11.2.0\dbhome_1\bin\oraclr11.dll") ) )LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = servername.company.se)(PORT = 1521)) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))))ADR_BASE_LISTENER = D:\oracleINBOUND_CONNECTION_TIMEOUT_LISTENER=180sqlnet.oraSQLNET.AUTHENTICATION_SERVICES= (NONE)SQLNET.INBOUND_CONNECT_TIMEOUT = 180ADR_BASE = D:\oracle\product\11.2.0\dbhome_1\logI am using VPN tunnel to connect to database from my client. I can ping server successfully. TNSPING to database works fine, but I am not able to connect to database. I get an error on client:ORA-12537 connection closed error.Alert log content is following:***********************************************************************Fatal NI connect error 12547, connecting to: (LOCAL=NO) VERSION INFORMATION:TNS for 64-bit Windows: Version 11.2.0.4.0 - ProductionOracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.4.0 - ProductionWindows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.4.0 - Production Time: 19-DEC-2013 13:
have a script to monitor the alert.log file for any ORA-xxxx errors. With 11g we found out many entries in regards of: Fatal NI connect error https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ 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 http://oracle.ittoolbox.com/groups/technical-functional/oracle-db-l/oracle-11g-linux-tns12535-errors-in-alert-log-5234974 TCP/IP NT Protocol Adapter for 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: fatal ni 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Error 12514 received logging on to the 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: fatal ni connect 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. Oracle also mentions the occurrence of this error if you use DB Console or Enterprise Manager to monitor your databases and the emagent will try to connect to the target database repeatedly and, statistically, some will fail (frequency will depend on how busy your system is). Most of the time (certainly for DB Console and Enterprise Manager Agent) the application will try to connect again and it will succeed. To fix the problem you could increase the value of SQLNE
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus bracke Dennis Stevenson Craig Borysowich DukeGanote Richard PCMag mircea_luca iudithm Nikki Klein Clinton Jones knowscognosdoi AbhaiTripathi Iqbalyk bluesguyAZ59 COMPANIES Dell Software Panaya Inc. Oracle VAI View All Topics View All Members View All Companies Toolbox for IT Topics Oracle Groups Ask a New Question Oracle Database This group is where peers share technical expertise, solve problems, and discuss issues related to the use of Oracle Databases, including Oracle Grid. Home | Invite Peers | More Oracle Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Oracle 11G Linux - TNS-12535 Errors in Alert Log Nate Himmons asked Jun 24, 2013 | Replies (30) Hello We are running Oracle11.2.0.1 on Red Hat Enterprise Linux Server release 5.8 (Tikanga). I see several time-out messages in our alert log. Also users are getting timed-ou