Re: SQL*Net & Developer 2000 networked app

In article <32149A67.1C2D_at_natinst.com>, davep_at_natinst.com says...
>
>Here's a weird one...
>
>I installed SQL*Net onto a computer that has never had Oracle installed
>on it so that I could see which files had been installed. There was the
>Oracle.ini, 5 DLLs in Windows\System, and the Oracle home (c:\orawin).
>So, I moved the Oracle home to a network volume (\\monsoon\temp). Then
>I copied our standard tnsnames.ora to the networked oracle home
>(\\monsoon\temp\orawin). Then I edited the local oracle.ini, changing

Do you mean \\monsoon\temp\orawin\network\admin ?

>all reference to c:\orawin to \\monsoon\temp. When I try to use it
>though, I get a tnsnames lookup failure.
>
>That may all seem normal, but then I went to my machine which runs
>Oracle & SQL*Net successfully. I deleted my oracle.ini and c:\orawin
>directory. Then I copied the oracle.ini from the computer mentioned
>above. I tried SQL*Net again, and it works! This is weird because I
>have no tnsnames on my computer and am using the same oracle.ini.
>
>What is going on?
>
>Dave
>--
>PS-What I am really trying to accomplish is a way to have my users using
>my dev 2000 apps from the server without too much on their hard drives
>and without running the oracle installer on each of their machines.
>________________________________________________________________________
>Dave Peckham
>IS Programmer/Analyst dave.peckham_at_natinst.com
>National Instruments http://www.natinst.com

I can't explain the behaviour you're seeing, but i can tell you how we effect a network installation. We run Netware with Win3.11 and Win95 clients.

First, from a dos window i do 'DIR /S/-P > TEMP1.TXT'. Then I map a network drive to a drive letter, run ORAINST and install to the network. Then i do 'DIR /S/-P > TEMP2.TXT'. Comparing temp1 and temp2 tells me what got changed locally. I create a subdirectory under ORAWIN called WINDOWS and copy any files that got created on my local drive into it, including the ORACLE.INI. Set up your tnsnames.ora,sqlnet.ora, tnsnav.ora, etc... on the file server.

The install machine should now be able to connect.

To setup a client, just copy all the orawin\windows files to their windows directory, add the ORA_CONFIG line to win.ini, set a path to the ORAWIN\BIN directory and reboot.

-- 
Tony Noble
tnoble_at_mt.gov
Opinions expressed do not necessarily reflect those of my employer.