Re: How to best distribute TNSNAMES.ORA file to many clients?

Dave,

You didn't say if you're clients are Windows 3.1 or Windows95...You can put the orawin or orawin95 dir on a Network drive that your users can read from. The manner in which the config is done to point to that drive depends on whether your clients are 16 bit or 32 bit. You can do both, but will need to set up to separate directory structures, each with their own windows network products installed (orawin & orawin95, etc.). 16 bit uses both the DOS PATH and the [Oracle} section in win.ini to point to the location of the client DLLs and the oracle.ini file (respectively). 32 bit uses the registry to point to the client DLLs and other info (setup on install). The other option is to use a remote shared registry, or merge the Oracle registry entries into each users registry. I have learned most of this throught trial and error the hard way, and through the suggestions of others.

Greg Grooms
DBA
PRC David K. Baux <dbaux_at_amfam.com> wrote in article <32FB88B9.1D68_at_amfam.com>...
> Hi everyone, probably a sillie question here, but I'm fairly new
> to Oracle:
>
> We're getting ready to implement an application to lots of
> end-users (> 200), and want to automate client software
> installation and configuration as much as possible. Some
> of the users already use Oracle, some will be brand new.
> Instead of having each end-user run SQL*Net Easy Configuration
> to set up or update their TNSNAMES.ORA file, I was hoping to
> distribute a "generic" TNSNAMES file that would include all
> possible SIDs any user could connect to.
>
> My problem is that it seems that there's no way to generate a
> TNSNAMES file for each client workstation without going through
> SQL*Net Easy Config, which is exactly what I'm trying to avoid
> having each end-user do. I get the familiar "failed to resolve
> service name", even though I know the prototype TNSNAMES file is
> syntactically correct. I've snooped around a bit, and come to
> the conclusion that maybe the TNSNAMES contents are compared
> with a \orant\network\cfg file, but all the doc I've read warns
> me (with bold type!) against hacking these files.
>
> Has anyone experienced a similar scenario? I can't believe what
> I'm trying to do should be so difficult, but then again, I'm an
> idealist <g>. Many thanks in advance.
>
> Cheers,
>
> Dave
>
Received on Tue Feb 11 1997 - 00:00:00 CST