Fatal Ni Connect Error 12514 Sqlnet.log
not currently know of service requested in connect descriptor / Fatal NI connect error 12514, connecting to /ns main err code: 12564 / TNS-12564: TNS:connection refused Error like Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=server1)(PORT=25000)))(CONNECT_DATA=(SERVICE_NAME=DBNAME1)(CID=(PROGRAM=oracle)(HOST=server1)(USER=)))) VERSION INFORMATION: TNS for HPUX: Version 11.2.0.3.0 - Production Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.2.0.3.0 - Production TCP/IP NT Protocol Adapter for HPUX: Version 11.2.0.3.0 - Production Time: 17-JUN-2013 11:08:30 Tracing not turned 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 Possible Causes : 1.) The listener is down. 2.)The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. 3.)This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Solution.: 1.) Check your listner by issueing "lsnrctl status" command. Verify if the listener is up and running. 2.) Verify your alert log and sqlnet.log to see if any errors. 3.) Verify if you have specified SID or SERVICE_NAME in you Global tnsnames.ora file. Correct it if not set properly. Posted by deepak aggarwal at 8:25 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Sub
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 Oracle Database Tips by Burleson Consulting 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? http://oraclehunterz.blogspot.com/2013/06/ora-12514-tnslistener-does-not.html 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: 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 http://www.dba-oracle.com/t_fatal_ni_connect_error_12170.htm 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 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 re+ 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 timed out +TNS-00505: http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html Operation timed out (with different ports), found in both RAC Instances Alert Log file. Problem: Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.3.0 - Production http://oracletechdba.blogspot.com/2015/06/primary-database-alertlog-giving-below.html 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 Tracing not turned on. Tns error fatal ni 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 what was causing the problem. Our database is behind fatal ni connect 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. Oracle also mention the occurrence of this error if you use DB Console or Enterprise Manager to monitor your databa
connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hostname)(PORT=port))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DBSID_DGB)(CID=(PROGRAM=oracle)(HOST=hostname)(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: 01-JUN-2015 11:12:47 Tracing not turned 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 Solution: When checking the service in DR using lsnrctl status, you are not able to see the service "DBSID_DGB". sologgedin to the Standby db and modify the parameter, SQL> alter system set "__dg_broker_service_names" = 'DBSID_DGB' scope=both; System altered. ++Check the values. SELECT a.ksppinm "Parameter",b.ksppstvl "Session Value",c.ksppstvl "Instance Value" FROM x$ksppi a, x$ksppcv b, x$ksppsv c WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/__dg%' escape '/' / ------------------ __dg_broker_service_names DBSID_DGB DBSID_DGB ++Then check the lsnrctl status,You can see the services("DBSID_DGB"). $lsnrctl status LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 01-JUN-2015 11:11:26 Copyright (c) 1991, 2010, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production Start Date 01-JUN-2015 10:29:23 Uptime 0 days 0 hr. 42 min. 2 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /u01/app/11.2.0/grid/network/admin/listener.ora Listener Log File /u01/app/diag/tnslsnr/za-fdbs-dr-03/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=prot))) Services Summary... Service "DBSID" has 1 instance(s). Instance "DBSID", status READY, has 1 handler(s) for this service... Service "DBSID_DGB" has 1 instance(s). Instance "DBSID", status READY, has 1 handler(s) for this service... ++Now in Primary alert log we are not getting any more warnings. Posted by Karl Marx at 02:24 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels:DATABASE,PERFORMANCE Database No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Categories Database (112) APPS DBA (35) EXADATA