Fatal Ni Connect Error 12541
Contents |
TNS:no listener | Lister is UP If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above
Fatal Ni Connect Error 12170 Tns-12535
to proceed. To start viewing messages, select the forum that you want to visit fatal ni connect error 12170 ora-3136 from the selection below. Results 1 to 8 of 8 Thread: TNS-12541: TNS:no listener | Lister is UP Tweet Thread Tools Show ns main err code: 12535 Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 02-15-2011,10:35 AM #1 poling View Profile View Forum Posts Junior Member Join Date Feb 2011 Posts
Nt Secondary Err Code: 60
4 TNS-12541: TNS:no listener | Lister is UP Hi, im struggling with a listener issue. I have several Oracle/SAP environments i am responsible for. Most of them run fine but on some i get the error: TNS-12541: TNS:no listener. On one of them this occurs quite a lot actually. So what is the case? Im running Oracle 10.2.04 on windows 2003, of course the listener is running (DUH). Also the tnsnames.ora sqlnet.ora and
Fatal Ni Connect Error 12637 Connecting To (local=no)
listener.ora are defined properly. Most of the cases it is not even causing issues (since it SAP is running on top of it). However some actions do start a process outside the SAP instance, like applying a SAP transport. And on those cases sometimes I get the above mentioned error. So I got suspicious and started a tnsping in a loop. It turns out the 12541 pops up quite regularly, enough to make me worried. The frequency change from several times a minute to once every couple of minutes. It doesn’t seems to be an network issue since a ping to wherever always goes fine. So I turned on tracing (in the listener.ora) on to level ADMIN, turns out there are no trace entries from the failed tnsping. I moved up the level to SUPPORT. Same, no trace entries, there is a time gap on the moments that tnsping fails. The same counts for the listener.log…no logging of the failed occurrences. Then I added a R3trans –d in the loop. Of course this check also fails every now and then and the following info I find in the sqlnet.log Fatal NI connect error 12541, connecting to: (DESCRIPTION=(SDU=32768)(ADDRESS=(COMMUNITY=SAP.WORLD)(PROTOCOL=TCP)(HOST=prd01)(PORT=1527))(CONNECT _DATA=(SID=PRD)(GLOBAL_NAME=PRD.WORLD)(CID=(PROGRAM=I:\usr\sap\PRD\SYS\exe\run\R3trans.exe)(HOST=PRD 01)(USER=prdadm)))) VERSION INFORMATION: TNS for 64-bit Windows: Version 10.2.0.2.0 - Production Windows NT TCP/IP NT Protocol Adapter for
have a script to monitor the alert.log file for any ORA-xxxx errors. With 11g we found out many entries in regards of: Fatal NI connect error The problem: alert.log file fatal ni connect error 12638 has many entries for Fatal NI connect error. Examples: *********************************************************************** Fatal NI connect
Nt Secondary Err Code: 110
error 12514, connecting 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: ns main err code: 12564 Version 11.2.0.2.0 - Production Time: 17-JAN-2011 10:20:45 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 http://www.dbasupport.com/forums/showthread.php?61789-TNS-12541-TNS-no-listener-Lister-is-UP 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 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 https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ 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, some will fail (frequency will depend on how busy your system is). Most of the time (certainly for DB Console and Enterprise Manager Agent) the application will try to connect again and it will succeed. To fix the problem you could increase the value of SQLNET.INBOUND_CONNECT_TIMEOUT on the listener.ora and the sqlnet.ora file located on the server side. If you already have a value you have considered adequate, you m
+ 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: Operation timed out http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html (with different ports), found in both RAC Instances Alert Log file. Problem: Fatal NI connect http://www.orafaq.com/forum/t/190397/ error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.3.0 - Production 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 struct: ns main fatal ni 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 a firewall. Firewall has an "idle session timeout" fatal ni connect 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 databases and the em agent will try to connect to the target database repeatedly and, statistically,
to friend Error with shipping redo log from primary to standby [message #601350] Tue, 19 November 2013 20:56 trantuananh24hg Messages: 666Registered: January 2007 Location: Ha Noi, Viet Nam Senior Member Good morning! I've got error yesterday. Let me describe: I configure DG successfully at 15/10/2013, both of them are Oracle 11gr2, ASM, RHEL 5 (single), they are fine till 19/11/2013 when system administrator change the IP of primary. So, I got error shipping redo log from primary to standby. P/S: Because of long brief, so I device into 2 post. I'm sorry for inconvenience Primary (RHEL 5.5, Oracle 11gr2 Grid Infrastructure, Enterprise) Error: Log Transport Services Error 2 1066 12504 YES 20-NOV-13 PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504. Log Transport Services Error 0 1067 12504 YES 20-NOV-13 Error 12504 received logging on to the standby Log Transport Services Error 2 1068 12504 YES 20-NOV-13 PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504. Log Transport Services Error 0 1069 12504 YES 20-NOV-13 Error 12504 received logging on to the standby Log Transport Services Error 2 1070 12504 YES 20-NOV-13 PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504. - error log file * alert log file: Fatal NI connect error 12541, connecting to: (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=)(CID=(PROGRAM=oracle)(HOST=webcharge)(USER=oracle)))(ADDRESS=(PROTOCOL=TCP)(HOST=10.54.5. 177)(PORT=1521))) VERSION INFORMATION: TNS for Linux: Version 11.2.0.1.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production Time: 19-NOV-2013 01:16:44 Tracing not turned on. Tns error struct: ns main err code: 12541 TNS-12541: TNS:no listener ns secondary err code: 12560 nt main err code: 511 TNS-12564: TNS:connection refused ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS