Re: SQLNet Round Robin

Chris:

This is exactly how it's sopposed to work. It does this because it thinks you have multiple listeners set up on the same server. The term is Client Load Balancing. It's great for improving database connection times, but as you've noticed, it defeats your purpose.

I'm not sure if there is a way to automatically do what you intend at the SQL level, perhaps you're better off using router tables to do this for you.

The dirty way is of course to create two database descriptions in your TNSNAMES.ORA file, and have your users manually change the DB they connect to if something should happen. <Ick!>

Regards,

Erik

In article <913976524.18484.0.nnrp-07.9e9817da_at_news.demon.co.uk>,   "Chris Dipple" <chris_at_chin.demon.co.uk> wrote:
> We are using SQLNet 2.1 and have two entries in the address list in
> TNSNAMES.ORA. The second entry is intended for use in the event of
> a disaster only.
>
> Our clients open a single connection for interactive use (ODBC) and
> occasionally
> for reporting purposes a second connection is opened. I would expect it to
> pick up
> the first entry in the address list but it always seems to pick up the
> second one (which
> is not normally active). If we add a third entry then it will pick this up
> on the next attempt,
> etc. It seems to be doing a round robin and there is no apparent way of
> stopping it.
>
> Does anyone know how to force it always to start from the first address
> entry???
>
> Chris
> chris_at_chin.demon.co.uk
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri Dec 18 1998 - 15:52:09 CST