Fatal Ni Connect Error 12170 Aix
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 Don Burleson Blog
fatal ni connect error 12170 firewall fatal ni connect error 12170 Oracle DatabaseNs Main Err Code: 12535
Tips by Burleson Consulting November 5, 2015 Question: Below error getting in alert log file every day, but database is working nt secondary err code: 110 fineWhat are the reason for this Fatal ni connect error 12170? Fatal NI connect error 12170. VERSION INFORMATION: TNS for 64-bit Windows: Version 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for 64-bit Windows: ns secondary err code: 12606 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 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
Fatal Ni Connect Error 12637
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 the Listener and the Oracle Database To Limit Resource Consumption By Unauthorized Users" for further information about setting the SQLNET.INBOUND_CONNECT_TIMEOUT parameter Action: If the error occurred due to system or network delays that are normal for the particular environment, then perform this steps:Turn on tracing to determine where cli
Fatal NI connect error 12547 [message #619535] Wed, 23 July 2014 04:30 Subbu19 Messages: 15Registered: July 2014 Location: Chennai Junior Member Hi, Following message oracle 12c fatal ni connect error 12170 occurs on alert.log file Fatal NI connect error 12547, connecting to: fatal ni connect error 12170 tns-12535 12606 (LOCAL=NO) VERSION INFORMATION: TNS for 64-bit Windows: Version 11.2.0.3.0 - Production Oracle Bequeath NT Protocol Adapter for 64-bit
Tns-00505: Operation Timed Out
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 on. Tns error struct: http://www.dba-oracle.com/t_fatal_ni_connect_error_12170.htm 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 12547 [message #619544 is a http://www.orafaq.com/forum/t/193730/ 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:operation timed out ns secondary err code: 12606 nt main err
11g às vezes encontramos no https://felipemorenodba.wordpress.com/2015/06/17/fatal-ni-connect-error-12170/ alert log mensagens monstruosas como esta: Fatal NI connect error 12170. VERSION INFORMATION: TNS for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production fatal ni Time: 16-JUN-2015 17:49:21 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: 78 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=172.80.27.176)(PORT=55534)) fatal ni connect Isto significa que por algum motivo a conexão entre o servidor de banco e o usuário foi abortada. Existe uma nota no My Oracle Support que dá uma sugestão muito interessante para analisar estes casos: Alert Log Errors: 12170 TNS-12535/TNS-00505: Operation Timed Out (Doc ID 1628949.1) Lá é sugerido usar o campo Client address presente na mensagem de erro para procurar no log do Listener o horário em que a conexão foi estabelecida. A porta que aparece é uma porta qualquer usada para comunicação. oracle@SERVIDOR >vgrep '(ADDRESS=(PROTOCOL=tcp)(HOST=172.80.27.176)(PORT=55534)' listener_orcl.log 16-JUN-2015 17:10:18 * CONNECT_DATA=(SID=ORCL)(SERVER=DEDICATED)(CID=(PROGRAM=safdw.exe)(HOST=BLEND09-PC)(USER=Blend09))) * (ADDRESS=(PROTOCOL=tcp)(HOST=172.80.27.176)(PORT=55534)) * establish * ORCL * 0 Com essa informação, temos uma noção de por quanto tempo a sessão ficou ativa. Neste caso, a conexão foi estabelecida em 16-JUN-2015 17:10:18 e finalizada em 16-JUN-2015 17:49:21. Uma prevenção para este problema é setar o parâmetro SQLNET.EXPIRE_TIME