Re: global tnsnames redundancy (7.3.4)
Date: 16 Jul 2001 01:08:09 -0700
Message-ID: <a20d28ee.0107160008.3e1a9f5b_at_posting.google.com>
bbgiesbre_at_home.com wrote in message news:<3b54ffb0.595675796_at_news1.rdc1.ab.wave.home.com>...
> Currently we are running several 7.3.4 databases (and a few 8.1x) and
> up to this point have been using local tnsnames. Due to growth we are
> wanting to move to a global tnsnames for administrative / update
> purposes, but have a major concern. If the master tnsnames server goes
> down (or is inaccessible to a particular network segment) then the
> users won't be able to access Oracle.
>
> I haven't had too much luck finding information on setting up
> redundant tnsnames for 7.3.4 other than a few references to the
> sql*net.ora configuration (no examples though).
>
> Is there a way to have multiple global tnsnames that would be accessed
> sequentially if the previous file was not accessible? What is the best
> way to do this in a mixed 7.3.4 - 8.1.x environment? Would this change
> at all if it was a purely 8.1.x environment (eventually we'll have to
> either upgrade or retire the 7.3.4 databases).
>
> Appreciate any pointers, or suggestions on where to find this
> information.
>
> Thanks,
>
> Brad
>
> (email responses remove leading b)
I have a better idea:
consider setting up Oracle Names, preferrably in an 8i instance, as
the interface has much improved.
With Oracle Names you can have multiple Names Servers. Your client
will fall back on the second Names Server when the first fails. Also
changes in one Names Server are automatically propagated to the
other(s). And you get free of charge global database links between all
your systems.
Regards,
Sybrand Bakker, Senior Oracle DBA Received on Mon Jul 16 2001 - 10:08:09 CEST