Re: Modifying tnsnames.ora without using SQLNet Configurator.

I heard that Oracle Names is eventually going to go away. I would look into using the Oracle Internet File System (iFS), which is currently released for Sun and NT. I haven't used it yet, but it looks like that is what Oracle is going to push.

Troy Meyerink
Raytheon
USGS/EROS Data Center
Sioux Falls, SD

Sybrand Bakker wrote:

> IMO, you'd better switch to Oracle Names
> In that cases you would configure
> names.directory_path = (onames, tnsnames)
> in sqlnet.ora
> You will have a correct onames setup and the end-user can retain their own
> tnsnames.ora.
> The other solution would be setting the tns_admin registry entry on all
> clients to point to a tnsnames.ora on a network drive, thus they will loose
> access to their tnsnames.ora.
>
> Hth,
>
> Sybrand Bakker, Oracle DBA
>
> H
> "Liam Caffrey" <eosys-nospam_at_eircom.net> wrote in message
> news:f9o75.3412$r4.2305_at_news.indigo.ie...
> > I need to be able to modify the tnsnames.ora with a text editor and change
> > the time whereever so that SQLNet Easy Configurator doesn't realise that
 the
> > file was changed by an entity of than the Configurator.
> >
> > Where does the configurator keep the the last edit timestamp, is it
 possible
> > to trick the Configurator into thinking that it made the change rather
 than
> > notepad.exe for example.
> >
> > I need to role out an application to about 100 users and I wanted to use
> > InstallShield to modify directly the tnsnames.ora file without the user
> > having to fiddle with the configurator. Is this possible?
> >
> > Maybe there is a more appropriate deployment strategy - network based
> > tnsnames.ora? Bear in mind that a lot of users will already be using their
> > own local tnsnames.ora with entries for other legacy Oracle instances.
> >
> > Regards
> >
> > Liam Caffrey
> > Change the "ten" to "net" before sending.
> > eosys_at_eircom.ten
> >
> >
> >
Received on Mon Jul 03 2000 - 00:00:00 CDT