Re: TNSNAMES.ora automating & consolidating
Date: Sat, 21 Jul 2001 21:42:34 GMT
Message-ID: <tgnqhbcknmcbe0_at_beta-news.demon.nl>
"Guy G" <guy_grice_at_dell.com> wrote in message
news:60c9b7c8.0105230830.128b315d_at_posting.google.com...
> "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
news:<tglti8e83tkof5_at_beta-news.demon.nl>...
> > Configure an Oracle Names server and don't bother about tnsnames.ora
> >
> > Hth,
> >
> > Sybrand Bakker, Oracle DBA
> >
> > "Guy G" <guy_grice_at_dell.com> wrote in message
> > news:60c9b7c8.0105221136.5c9b47bc_at_posting.google.com...
> > > Anyone have any experience consolidating the TNSNAMES.ora file to be
> > > controlled and maintained on one database and prevent duplication
> > > through automation. ActiveX is not an alternative as it is not turned
> > > on on all Win2k DB servers.
> > > Thx
>
>
> How does this play in if you already have an existing 20,000 users
> runing on the C:\ORACLE\NETWORK\ADMIN\TNSNAMES.ora
Send them an updated sqlnet.ora with
names.directory_path = (onames, tnsnames)
and names.preferred_servers = <your names server>
(The net assistants will do that for you)
zip, convert it to an executable and e-mail it to them.
The tnsnames.ora will not be used anymore with this setup and you can
maintain your config centrally, which is the most significant advantage of
Oracle Names.
I for me wouldn't have distributed a tnsnames.ora to 20.000 people, as I am
aware which administration headaches result from it. Hundred is already a
challenge.
Apparently the disaster already happened.
Regards,
Sybrand Bakker, Oracle DBA Received on Sat Jul 21 2001 - 23:42:34 CEST