The system I am working on includes redundant servers and redundant connections between them.
Each machine has dual NICs, each connected to separate switches.
Any NIC/switch can be disable and the system should still work.
Each server has 2 ip addresses, one for each NIC and Oracle on the server
may be accessed via SQLNet at either address.

The problem I have having is that when a switch/NIC is disabled, the SQL*Net
client takes 3m 9s to time out. How do I get it to time out quicker (i.e. within
seconds) if the ip address it is trying to connect to is inaccessible?

Thanks in advance.

Werner

Hi Werner,

>> The system I am working on includes redundant servers

You mean RAC?

In RAC, you use TAF to set the time before failing over to standby server:

http://www.dba-oracle.com/real_application...c_grid/taf.html

*******************************************************
>> How do I get it to time out quicker (i.e. within seconds) if the ip address it is trying to connect to is inaccessible?

See here:

http://www.dba-oracle.com/t_timeout_dead_o...le_sessions.htm

Not RAC. Just oracle standard edition and a few programs with update the servers and a pair of
PHP web servers.

I'll have a look at the links you provided. Really, what I am looking for is how to make sqlclient
timeout quickly when it tries to connect to a server with an inaccessible IP address. All the
timeout info I've come across relates to the server timing out when the client does not respond
or when it is inactive.

I guess I could put a wrapper around the sql connect to try to ping the ip address... but I thought
there would be a way to have sqlnet do this.

why arent you teaming / bonding the NIC so you dont have to worry about it