Re: Forcing tnsname.ora path

Ed Stevens <nospam_at_noway.nohow> wrote in message news:<4pe45v45h33b0bjhnk4s6kluso8rs35fu4_at_4ax.com>...
> On Tue, 18 Feb 2003 08:56:48 -0000, "Andrew Hardy"
> <spam.from.news_at_AdvanticaTech.com> wrote:
>
> ><mdeglin_at_partner.auchan.fr> wrote in message
> >news:b2sonr$imd$1_at_reader1.imaginet.fr...
> >
> >>I know the tnsname.ora path could be forced when modifying the registry
> .... but I don't know what is the exact modification !
> >>Can anybody help me ?
> >
> >Easiest way is to have a TNS_ADMIN in your environment settings (set to the
> >directory containing your tnsnames.ora), no messing about with the registry.
> >
> >Andy
> >
>
> Conversly, one could say 'Easiest way is to have TNS_ADMIN (set to the
> directory containing your tnsnames.ora) in your registry
> (HKLM\software\oracle), no messing arbout with the environment
> settings.
>
> I don't know what the pros and cons are of using the environment
> setting vs. the registry in this case. But I don't see it as an ease
> of use issue, as implied by 'no messing about with . . .'
>
> In the one case, I open a windows tool and type in
> 'tns_admin=c:\oracle\network\admin' (or whatever the path is). In
> the other case, I open a windows tool and type in
> 'tns_admin=c:\oracle\network\admin' (or whatever the path is).
>
> Comment not meant as a flame, just an observation.

One advantage of setting tns_admin in the environment rather than in the registry is that a network logon script can set the environment variable to a network tns file location, and no change has to be made in the registry if the location is changed due to disk problems, upgrades, etc ....

The network based tnsnames.ora file provides the advantage of providing one place where connect information has to be changed in the event of database migration, sid or service name change, hostname etc....

• Mark D Powell --