Home » RDBMS Server » Networking and Gateways » Very slow LSNRCTL - listener response time (Oracle RDBMS - 10.2.0.4, Win 64 2003, RAC, ASM )
Very slow LSNRCTL - listener response time [message #419696] Tue, 25 August 2009 04:04 Go to next message
hristo
Messages: 258
Registered: May 2007
Senior Member
Hi!

Im having a strange problem on one of my nodes in a three node RAC.

Grid Control suddenly reports this:


Failed to connect to database instance: ORA-12547: TNS:lost contact (DBD ERROR: OCIServerAttach).



I use LSNRCTL to check the listener. It takes for ever to complete the folowing commands: services and status.

The listener response time seems very high.

Grid Control reported this during some time:


The listener is down: LSNRCTL for 64-bit Windows: Version 10.2.0.4.0 - Production on 25-AUG-2009 10:30:12 Copyright (c) 1991, 2007, Oracle. All rights reserved. Welcome to LSNRCTL, type "help" for information. LSNRCTL> Connecting to (ADDRESS=(PROTOCOL=TCP)(HOST=xxx)(PORT=1521)) TNS-12547: TNS:lost contact TNS-12560: TNS:protocol adapter error TNS-00517: Lost contact 64-bit Windows Error: 54: Unknown error LSNRCTL> .



I have restarted the listener, but the problem came back. There are nothing in the listener.log/SQLnet.log.

I can log in on the affected node, but it takes over one minute.

What can be wrong?

Regards
Hristo

[Updated on: Tue, 25 August 2009 06:22]

Report message to a moderator

Re: Very slow LSNRCTL - listener response time [message #419729 is a reply to message #419696] Tue, 25 August 2009 06:24 Go to previous messageGo to next message
hristo
Messages: 258
Registered: May 2007
Senior Member
Hi!

I found out that unknown error 54 = net helpmsg 54

The network is busy

So, any idea where to look now?

Regards
Hristo
Re: Very slow LSNRCTL - listener response time [message #419744 is a reply to message #419696] Tue, 25 August 2009 07:45 Go to previous messageGo to next message
hristo
Messages: 258
Registered: May 2007
Senior Member
Hello again!

Found this on metalink:

Error Description: 
ERROR_NETWORK_BUSY 
54 
0x36 
The network is busy. 

Cause: 
This indicates a bottleneck at the network layer(TCP/IP). 

Action: 
1.Try increasing dispatchers and shared servers. 


Is there a way to verify that this is the problem?

Regards
Hristo
Re: Very slow LSNRCTL - listener response time [message #419772 is a reply to message #419696] Tue, 25 August 2009 09:49 Go to previous messageGo to next message
BlackSwan
Messages: 25050
Registered: January 2009
Location: SoCal
Senior Member
Does any of this reside in/on a virtual system?
If so, which part(s) and what VM name & version?
Re: Very slow LSNRCTL - listener response time [message #419773 is a reply to message #419772] Tue, 25 August 2009 09:52 Go to previous messageGo to next message
hristo
Messages: 258
Registered: May 2007
Senior Member
Hi!

No, it does not.

Regards
Hristo
Re: Very slow LSNRCTL - listener response time [message #419893 is a reply to message #419696] Wed, 26 August 2009 01:20 Go to previous messageGo to next message
hristo
Messages: 258
Registered: May 2007
Senior Member
Hi again!

I tried to restart the listener yesterday. The same problem came back. Then I checked the listener.log more closely.

I found this:

25-AUG-2009 10:20:29 * services * 12537
TNS-12537: TNS: Anslutningen stängd
 TNS-12560: TNS: protokolladapterfel
  TNS-00507: Anslutningen stängd
   64-bit Windows Error: 232: Unknown error

TNS-12571: TNS: Fel vid lagring av paket
 TNS-12560: TNS: protokolladapterfel
  TNS-00530: Protokolladapterfel
   64-bit Windows Error: 54: Unknown error
    TNS-12518: TNS: Lyssnaren kunde inte överlämna klientanslutning
     TNS-12560: TNS: protokolladapterfel
      TNS-00530: Protokolladapterfel
       64-bit Windows Error: 233: Unknown error

TNS-12518: TNS: Lyssnaren kunde inte överlämna klientanslutning
 TNS-12560: TNS: protokolladapterfel
  TNS-00530: Protokolladapterfel
   64-bit Windows Error: 233: Unknown error



Regards
Hristo
Re: Very slow LSNRCTL - listener response time [message #419921 is a reply to message #419696] Wed, 26 August 2009 03:36 Go to previous message
hristo
Messages: 258
Registered: May 2007
Senior Member
Hello again!

I have solved the issue!

It was lack of available memory on the server that caused the listener to behave in the way it did.

More info at metalink doc:371983.1

Regards
Hristo
Previous Topic: Getting data from db2
Next Topic: Two Oracle server on same unix box can have same listener port or different listener port?
Goto Forum:
  


Current Time: Fri Dec 09 17:53:45 CST 2016

Total time taken to generate the page: 0.34244 seconds