RE: Long connect time when one node in RAC goes down

From: freek D'Hooge <>
Date: Wed, 3 Sep 2008 00:30:25 +0200
Message-ID: <000f01c90d4b$7eb306e0$>


Can you post the output of the lsnrctl status command? What I would like to see is which ip address is used by an instance to registrate to the remote listener. It could be that your session was connection at node 1, but was redirected to node 2 (due to server load balancing), but was given the real address of node 2 instead of the vip address.

Controlling which ip will be used (real or vip) is done via the local_listener parameter.


Freek D'Hooge
Oracle Database Administrator
tel +32(0)3 451 23 82

-----Original Message-----

From: [] On Behalf Of Yechiel Adar
Sent: dinsdag 2 september 2008 18:20
Subject: Re: Long connect time when one node in RAC goes down

Hello Mark

We connect from the client with failover and load balance to vip-node1 and vip-node2.
We pulled the plug on node2.
Oracle moved vip-node2 to node1, of course there is no listener on that address + port in node1.
We run connections with trace and found out that whenever we access via vip-node2 we have two errors in the trace file: 1) 12541 - no listener - (as expected) takes about 1 second to return the error.
2) 12535 - tns time out - takes about 6-7 seconds to return the error.

After the error, sql net use vip-node1 and make a connection.

We would like to eliminate the 12535 errors and shorted the 1 second for the 12541.

I do not see where the local listener and remote listeners as of any concern here.

Adar Yechiel
Rechovot, Israel

-- Received on Tue Sep 02 2008 - 17:30:25 CDT

Original text of this message