Fatal Ni Connect Error 12541 Windows
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 fatal ni connect error 12170 tns-12535 register link above to proceed. To start viewing messages, select the forum that you
Fatal Ni Connect Error 12170 Ora-3136
want to visit from the selection below. Results 1 to 8 of 8 Thread: TNS-12541: TNS:no listener | Lister is UP ns main err code: 12535 Tweet Thread Tools Show 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 nt secondary err code: 60 Join Date Feb 2011 Posts 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
Fatal Ni Connect Error 12637
is running (DUH). Also the tnsnames.ora sqlnet.ora and 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 INFORM
+ Solutions etc. Wednesday, August 20, 2014 Removing Fatal NI connect error 12170 from Database Alert Log In our one of the 11gR2 Production fatal ni connect error 12638 Database, there were so many entries w.r.tFatal NI connect error 12170 sqlnet.inbound_connect_timeout default + TNS-12535: TNS:operation timed out +TNS-00505: Operation timed out (with different ports), found in both RAC Instances
Nt Secondary Err Code: 110
Alert Log file. Problem: Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.3.0 - Production Oracle http://www.dbasupport.com/forums/showthread.php?61789-TNS-12541-TNS-no-listener-Lister-is-UP 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 err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 http://manishnashikkar.blogspot.com/2014/08/removing-fatal-ni-connect-error-12170.html 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" 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
Fatal NI connect error 12547 [message #619535] Wed, 23 July 2014 04:30 Subbu19 Messages: 15Registered: July 2014 Location: Chennai http://www.orafaq.com/forum/t/193730/ Junior Member Hi, Following message occurs on alert.log file Fatal NI connect error 12547, connecting to: (LOCAL=NO) 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 fatal ni Time: 23-JUL-2014 04:18:15 Tracing not turned on. Tns error struct: 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 fatal ni connect a moderator Re: Fatal NI connect error 12547 [message #619544 is a 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