Fatal Ni Connect Error 12170 Oracle 11g
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 error 12170 + TNS-12535: TNS:operation fatal ni connect error 12170 firewall timed out +TNS-00505: Operation timed out (with different ports), found in both RAC Instances fatal ni connect error 12170 ora-3136 Alert Log file. Problem: Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.3.0 - ns main err code: 12535 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: 20-AUG-2014 14:17:36 fatal ni connect error 12637 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 message was repeating during whole day almost for every application server.I've finally found
Oracle 12c Fatal Ni Connect Error 12170
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 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. O
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.
Nt Secondary Err Code: 110
Please enter a title. You can not post a blank message. ns main err code 12535 oracle 11g Please type your message and try again. More discussions in General Database Discussions All PlacesDatabaseGeneral Database Discussions This fatal ni connect error 12170 sap discussion is archived 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 http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html with connection problem on 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) https://community.oracle.com/thread/2614609 and SQL Developer.Content of tnsnames, listener 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 Protoc
12, 2016 - 3:19 am UTC Category: Database – Version: 11.2.0.1 Latest Followup You Asked Hi tom, In our oracle database setup frequently getting error like - Fatal NI https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:9530823800346907304 connect error 12537, connecting to: (LOCAL=NO) 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 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production Time: 27-JUL-2016 17:24:10 Tracing not turned on. Tns error struct: ns main err code: 12537 TNS-12537: TNS:connection closed ns secondary err code: 12560 nt main err code: fatal ni 0 nt secondary err code: 0 nt OS err code: 0 opiodr aborting process unknown ospid (9352) as a result of ORA-609 and we said... From MOS 1538717.1 ================================================== Alert.log shows ORA-609 with TNS-12537: TNS:connection closed (Doc ID 1538717.1) APPLIES TO: Oracle Net Services - Version 11.2.0.1 to 11.2.0.4 [Release 11.2] Oracle Net Services - Version 12.1.0.2 to 12.1.0.2 [Release 12.1] Information fatal ni connect in this document applies to any platform. SYMPTOMS Alert log shows failed incoming connection: Fatal NI connect error 12537, connecting to: (LOCAL=NO) 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: 26-FEB-2013 02:23:51 Tracing not turned on. Tns error struct: ns main err code: 12537 TNS-12537: TNS:connection closed ns secondary err code: 12560 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 opiodr aborting process unknown ospid (28725) as a result of ORA-609 CAUSE First an explanation of this kind of errors. The message opiodr aborting process unknown ospid (.....) as a result of ORA-609 is just a notification that oracle database closed (aborted) a dedicated process because of ORA-609. ORA-609 means "could not attach to incoming connection" so the database process was 'aborted' (closed) because it couldn't attach to the incoming connection passed to it by the listener. The reason for this is found in the sqlnet error stack, in our case is: TNS-12537: TNS:connection closed. Ba