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

  • From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>
  • To: "'adar666@xxxxxxxxxxxx'" <adar666@xxxxxxxxxxxx>
  • Date: Tue, 2 Sep 2008 11:23:46 -0400

Are you sure you are referencing *only* the VIP, and *NOT* the physical IP, not 
only in the connect string definition, but also in the local_listener, and 
remote_listener parameter, on all nodes?  Please check all of these.


Mark J. Bobak
Senior Database Administrator, System & Product Technologies
789 E. Eisenhower, Parkway, P.O. Box 1346
Ann Arbor MI 48106-1346
+1.734.997.4059  or +1.800.521.0600 x 4059

ProQuest...Start here.

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Yechiel Adar
Sent: Tuesday, September 02, 2008 11:18 AM
Subject: Re: Long connect time when one node in RAC goes down

Problem update:

We run trace level=16 and found that failover works fine. The client
immediately get: NO LISTENER and fails over as expected.
 From time to time the response is bad and we get: TNS TIME OUT instead

Adar Yechiel
Rechovot, Israel

Yechiel Adar wrote:
> We need some help.
> RAC, Oracle on windows 2003 servers  64 bit.
> We did a fail over test. We disconnected one server from the network
> by pulling the network cable.
> The system worked fine, but once in a while a connection will take 6
> seconds instead on 20 ms.
> We understand that this happens because the VIP is moved to the second
> computer and there is
> nothing there to handle calls on that TCP address.
> I would like to know how to shorten the time from 6 seconds to almost
> nothing.


Other related posts: