Re: Long connect time when one node in RAC goes down
Date: Thu, 4 Sep 2008 11:07:10 -0400
I second Martin,
Seems like ARP refresh issue. So it's not name to IP address (because that pair doesn't change and you most likely getting it from client cache anyway), but IP to MAC resolution. With sysadmin help and tool like snoop it could be narrowed down.
On 9/4/08, Martin Klier <usn_at_usn-it.de> wrote:
> Hi Yechiel,
> Yechiel Adar schrieb:
> > After that it try to convert the name to tcp/ip address.
> > When sqlnet try to convert server2-vip to tcp/ip address he is stuck.
> > It seems that somewhere in the network something is not updated
> > when the vip is moved to the other node and it takes about 6 (or 6*2)
> > seconds
> > until sqlnet gets error from the network and then it try to connect with
> > the second entry, server-vip1, and this works.
> > Have you heard anything about this problem?
> It sounds a bit like an ARP refreshing issue. On large networks, the ARP
> caches of the switches might take their time to refresh their tables,
> and the more intermediate switch/routing stations/paths are different
> from "client" to the DB, the longer it might take to renew them.
> Can you or your network admin trace the managed switches that are
> immediately involved on client and server side?
> Usn's IT Blog for Linux, Oracle, Asterisk