Fatal Ni Connect Error 12170
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 firewall Don Burleson Blog
fatal ni connect error 12170 ora-3136 fatal ni connect error 12170 Oracle Database Tips by Burleson Consulting November 5, 2015 Question: BelowNs Main Err Code: 12535
error getting in alert log file every day, but database is working fineWhat are the reason for this Fatal ni connect error 12170? Fatal NI connect error 12170. VERSION INFORMATION:
Fatal Ni Connect Error 12637
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 - Production Time: 28-MAY-2012 19:20:02 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 Answer: The fatal nt secondary err code: 110 ni connect error 12170 is related to the ORA-12170 error: ORA-12170: TNS:Connect timeout occurredCause: The client failed to establish a connection and complete authentication in the time specified by the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in the sqlnet.ora file. This error may be a result of network or system delays, or it may indicate that a malicious client is trying to cause a denial-of-service attack on the database server. The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP). See Also: "Configuring
Fatal NI connect error 12547 [message #619535] Wed, 23 July 2014 04:30 Subbu19 Messages: 15Registered: July 2014 Location: Chennai Junior Member Hi,
Oracle 12c Fatal Ni Connect Error 12170
Following message occurs on alert.log file Fatal NI connect error 12547, sqlnet.inbound_connect_timeout default connecting to: (LOCAL=NO) VERSION INFORMATION: TNS for 64-bit Windows: Version 11.2.0.3.0 - Production Oracle Bequeath NT Protocol fatal ni connect error 12638 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 04:18:15 Tracing not turned http://www.dba-oracle.com/t_fatal_ni_connect_error_12170.htm 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 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 http://www.orafaq.com/forum/t/193730/ 12547 [message #619544 is a reply to message #619535] Wed, 23 July 2014 05:11 Michel Cadot Messages: 63883Registered: March 2007 Location: Nanterre, France, http://... Senior MemberAccount Moderator ORA-12547: TNS:lost contact *Cause: Partner has unexpectedly gone 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:op
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 https://community.oracle.com/thread/2614609 page. Please enter a title. You can not post a blank message. http://dbaforums.org/oracle/index.php?showtopic=22440 Please type your message and try again. More discussions in General Database Discussions All PlacesDatabaseGeneral Database Discussions This 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 fatal ni stakk 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 fatal ni connect (sqlplus username/password@tns_alias) 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 - ProductionWind
Joined: 22-April 13 Member No.: 48,503 Frequently getting below error in alert log file. Please help me to sort out this issue. Database: Active standby database OS: Windows Server Db Version: 11.2.0.2 Error: *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for 64-bit Windows: Version 11.2.0.2.0 - Production Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.2.0 - Production Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.2.0 - Production Time: 26-APR-2013 01:02:43 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.47.111.12)(PORT=49753)) WARNING: inbound connection timed out (ORA-3136) Tns error struct: Time: 26-APR-2013 01:02:43 ns main err code: 12535 Tracing not turned on. Tns error struct: TNS-12535: TNS:operation timed out ns main err code: 12535 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.47.111.12)(PORT=49765)) WARNING: inbound connection timed out (ORA-3136) nt secondary err code: 0 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.47.111.12)(PORT=49776)) WARNING: inbound connection timed out (ORA-3136) burleson View Member Profile Apr 27 2013, 05:05 PM Post #2 Advanced Member Group: Members Posts: 13,227 Joined: 26-January 04 Member No.: 13 Hi Yogi,>> TNS-12535http://www.dba-oracle.com/t_ora_12535_tns_...n_timed_out.htmTo diagnose a ORA-12535 error, follow these steps to ensure connectivity to Oracle:1 - Check your client-side sqlnet log files for more details2 - Try a direct connection from your client using tnsping:tnsping