Oracle-L: Re: tnsnames and sqlnet connectivity question

From: Tim Gorman <Tim_at_SageLogix.com>
Date: Sat, 26 Oct 2002 08:08:48 -0800
Message-ID: <F001.004F499C.20021026080848@fatcity.com>

tnsnames and sqlnet connectivity questionThe socket 6521 cannot be active on "apollo", so you'll either have to take the TNS Listener down along with the instance or restart the TNS Listener so that it is not listening on that socket after taking the instance down. Taking the entire "apollo" machine down is another way to accomplish this... :-)

It seems reasonable that the TNS Listener should have functionality to fail immediately (or there should be a configurable timeout) with some kind of error message if the desired database instance isn't available, but it doesn't seem to work that way.

The "listener.ora" parameter CONNECT_TIMEOUT_<lsnr-name> seems like it should be a good candidate for this, but instead it seems to be a timer in the TNS Listener that starts when a connection request first starts and ends when connection is established. In other words, it is a protection mechanism against slow clients or slow WANs tying up the TNS Listener process on each connection attempt, establishing an upper-limit in which to completely establish a connection. The default value of "0" seconds means "indefinite". Unfortunately, this all doesn't seem to translate into functionality where the TNS Listener process "times itself out" if it can't establish the connection within a certain period, oddly enough...

C'est la vie...

Original Message ----- From: Jamadagni, Rajendra To: Multiple recipients of list ORACLE-L Sent: Saturday, October 26, 2002 8:58 AM Subject: tnsnames and sqlnet connectivity question

suppose I have an entry like this in tnsnames.ora ...

ESSNCS =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = apollo)(PORT = 6521))
(ADDRESS = (PROTOCOL = TCP)(HOST = aquarius)(PORT = 6521))
)))

I try to connect to ESSNCS and (assume) apollo instance is down, it seems sqlnet takes a long time to see if it will connect to apollo and then connect to aquarius. But if apollo machine is down (i.e. no network connectivity), it promptly goes to aquarius.

How can we reduce the time that sqlnet waits to make a connection to apollo and immediately goes to aquarius? I'd like that time to be about 5 to 6 seconds ...

Thanks
Raj

Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art!

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Tim Gorman
  INET: Tim_at_SageLogix.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Received on Sat Oct 26 2002 - 11:08:48 CDT