Fatal Ni Connect Error 12170 Solaris
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 fatal ni connect error 12170 Oracle Database Tips by Burleson Consulting November 5, 2015 Question: Below ns 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:Nt Secondary Err Code: 110
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 ni
Ns Secondary Err Code: 12606
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 the Listener an
to Oracle 11.2.0.3 I am seeing the following messages in the alert log repeatedly. I didnât see these messages in 10g databases. I tried tracking down the IP tns-00505: operation timed out address but found out that these were computers, which had been accessing
Fatal Ni Connect Error 12637
the database for many years. But these messages are being logged into the alter log only after the fatal ni connect error 12170 tns-12535 12606 upgrade to 11.2.0.3.Is it a known behavior in Oracle 11gR2? I did some checking with documentation but couldnât find any explanation. So any help will be appreciated.Thanks,Ashoke MandalFatal NI connect http://www.dba-oracle.com/t_fatal_ni_connect_error_12170.htm error 12170.VERSION INFORMATION:TNS for Solaris: Version 11.2.0.3.0 - ProductionOracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - ProductionTCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - ProductionTime: 16-APR-2015 06:54:01Tracing not turned on.Tns error struct:ns main err code: 12535TNS-12535: TNS:operation timed outns secondary err code: 12560nt main err code: 505TNS-00505: Operation timed outnt secondary err code: 145nt OS err code: 0Client http://oracle-l.freelists.narkive.com/MhYvZ6TK/fatal-ni-connect-error-12170-in-alert-of-oracle-11gr2-database address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.72.216.138)(PORT=54551))Thu Apr 16 06:54:01 2015[CONFIDENTIALITY AND PRIVACY NOTICE]Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records.To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com Sweetser, Joe 2015-05-11 20:37:51 UTC PermalinkRaw Message Most likely nothing to be too concerned about. Take a peek at on Metalink/MOS:Fatal NI Connect Error 12170, 'TNS-12535: TNS:operation timed out' Reported in 11g Alert Log (Doc ID 1286376.1)-joeFrom: oracle-l-***@freelists.org [mailto:oracle-l-***@freelists.org] On Behalf Of Mandal, AshokeSent: Monday, May 11, 2015 2:32 PMTo: oracle-l-***@freelists.orgCc: oracle-***@freelists.orgSubject: F
friend Fatal NI connect error 12170. [message #623271] Sun, 07 September 2014 12:28 janakors Messages: 180Registered: http://www.orafaq.com/forum/t/194350/ September 2009 Senior Member hi i used to get this error in my alert log some time and it is frequent like every two weeks or sometime after a month *********************************************************************** Thu Sep 04 12:11:23 2014 *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for Solaris: Version 11.2.0.3.0 fatal ni - Production Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production Fatal NI connect error 12170. Time: 04-SEP-2014 12:11:23 Tracing not turned on. Tns error struct: VERSION INFORMATION: TNS for Solaris: Version 11.2.0.3.0 - Production Oracle Bequeath fatal ni connect NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production ns main err code: 12535 Time: 04-SEP-2014 12:11:23 TNS-12535: TNS:operation timed out Tracing not turned on. ns secondary err code: 12560 nt main err code: 505 Tns error struct: TNS-00505: Operation timed out ns main err code: 12535 nt secondary err code: 145 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.x.xx.16)(PORT=111)) 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: 145 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.xx.xx.16)(PORT=112) Thu Sep 04 12:19:12 2014 *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for Solaris: Version 11.2.0.3.0 - Production Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production Time: 04-SEP-2014