Fatal Ni Connect Error 12519
Contents |
have a script to monitor the alert.log file for any ORA-xxxx errors. With 11g we found out many fatal ni connect error 12170 tns-12535 entries in regards of: Fatal NI connect error The problem: alert.log
Fatal Ni Connect Error 12170 Ora-3136
file has many entries for Fatal NI connect error. Examples: *********************************************************************** Fatal NI connect error 12514, connecting ns main err code: 12535 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 TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production Time: 17-JAN-2011 10:20:45 Tracing not turned fatal ni connect error 12637 connecting to (local=no) on. Tns error struct: ns main err code: 12564 TNS-12564: TNS:connection refused ns secondary err code: 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
Tns-12564: Tns:connection Refused
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: 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
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 ns main err code: 12564 Ion Excel-DB Don Burleson Blog
fatal ni connect error 12638 fatal ni connect error 12170 Oracle Database Tips by Burleson ConsultingFatal Ni Connect Error 12547 Connecting To Local No
November 5, 2015 Question: Below error getting in alert log file every day, but database is working fineWhat are the reason for this Fatal ni connect error 12170? Fatal https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ 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: 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 http://www.dba-oracle.com/t_fatal_ni_connect_error_12170.htm 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 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 log
6 ------------ Then the listener looks like this: LSNRCTL> services Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ultra1)(PORT=1521))) Services Summary... PLSExtProc has 1 service handler(s) DEDICATED SERVER established:0 refused:0 http://www.dbasupport.com/forums/printthread.php?t=29625 LOCAL SERVER DB01 has 1 service handler(s) DEDICATED SERVER established:3 refused:0 LOCAL SERVER DB01 has 2 service handler(s) DISPATCHER established:0 refused:0 current:0 max:1022 state:ready D000 (ADDRESS=(PROTOCOL=tcp)(HOST=ultra1)(PORT=32799)) DEDICATED SERVER established:0 refused:0 LOCAL SERVER The command completed successfullysfully So seems all the connections are directed to DEDICATED SERVER !! And I checked the v$circuit, I got nothing fatal ni there. What's wrong here? I think it should be using MTS! here are my tnsnames.ora DB01.ULTRA1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.5.153)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = DB01) (INSTANCE_NAME = DB01) ) ) 09-19-2002, 11:09 AM gandolf989 Each client needs to be configured to use MTS. I fatal ni connect think that the default connection is usually dedicated. You may want to look at the network files for some of your clients. You may even find that they are hardcoded to be dedicated. 09-19-2002, 11:19 AM Rems Default connection is not DEDICATED. If You don't set in tnsnames.ora to use DEDICATED, client will use MTS, if database is MTS. Rems, DBA from Latvia 09-19-2002, 11:45 AM skatergou I edited the tnsnames.ora on the client to the follows: DB01.ULTRA1 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.5.153)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = DB01) (INSTANCE_NAME = DB01) (SRVR = SHARED) ) I think it should use MTS this time. But It failed to even connect! got this: ERROR: ORA-12519: TNS: no appropriate service handler found. From the log I got this: *********************************************************************** Fatal NI connect error 12519, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.1.5.153)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=DB01)(I NSTANCE_NAME=DB01)(SRVR=SHARED)(CID=(PROGRAM=C:\Oracle\Ora81\bin\SQLPLUS.EXE)(HOST=ASSET36540)(USER= YIHONG)))) VERSION INFORMATION: TNS for 32-bit Windows: Version 8.1.6.0.0 - Production Windows NT TCP/IP NT Protocol Adapter f