Document ID: 12116.1
Subject: INSTALLING SQL*NET FOR WINDOWS ONTO A NETWORK DRIVE
Last Modified: 26 September 1996
Author: Unknown
-------------------------------------------------------------------------------
Installing SQL*Net for Windows ONTO a Network Drive
This bulletin outlines the steps and explains some of the issues involved when
installing SQL*Net for Windows on a network drive with the V3 Installer
for Windows. Much of the information contained in this bulletin is covered in
an appendix in the installation manuals for the CDE (Cooperative Development
Environment) tools like Oracle Forms, v4.
Please note that the installation procedure described in this bulletin is
known to work on Novell NetWare LAN's. Following these steps may work on other
LAN systems. However, Oracle does not support installing any of its products
for Windows on any LAN other than Novell NetWare at this time.
***IMPORTANT: If you install SQL*Net for Windows on a network drive, you MUST
also install on the network drive in the same directory any other V3
installable Oracle Windows products that you plan to use.
Setting Up the File Server
--------------------------
1. Choose a workstation to use to install the Oracle products on the file
server. On that workstation, map a drive to an existing file server
drive and directory where you will install the Oracle products.
To map a drive to Novell NetWare, complete the following steps:
a) Log on to the LAN using an account with Read, Write, Create,
Modify, and File Scan priveleges.
b) Enter the following command:
MAP ROOT x:=volume_name:\file_server_directory
where x is the drive that you are mapping to the file server,
volume_name is the name of a volume on the file server, and
file_server_directory is the directory where you will install
the Oracle products.
2. Use the Oracle Installer to install the Oracle software on the file server.
Follow the installation instructions in the Installation Guide for the
product you are installing.
Notes:
a) when the Oracle Installer prompts you for a complete path to which
you wish to install Oracle products, you should enter the path
using the drive letter you mapped to the file server in the
previous step. Do not attempt to specify file_server, volume_name,
or file_server_directory.
b) all V3 installable Windows products must be installed in the same
Oracle home directory, so if you install one product on the network
drive, you must install all of the products on the network drive.
3. Copy the ORACLE.INI file created in your Windows directory into your
Oracle home directory.
4. Set the file attributes to allow concurrent access. On a NetWare file
server, if your Oracle home directory is F:\ORAWIN and you wanted to grant
access to the group EVERYONE, you would enter the following command:
GRANT R F FOR F:\ORAWIN TO EVERYONE
Setting Up the Client Workstations
----------------------------------
1. Set up a local ORACLE.INI file. Copy the ORACLE.INI from the Oracle home
directory on the network drive (see step 3 above) to the client
workstation's Windows directory.
2. If the client workstation uses a different drive letter mapping for the
Oracle home directory than the mapping used at installation time, then
edit the ORACLE.INI file to reference the correct drive letter.
3. Modify the WIN.INI in the client workstation's Windows directory to add
the [Oracle] section. If the ORACLE.INI was copied to the C:\WINDOWS
directory on the client workstation, you would add the following lines
to the WIN.INI:
[Oracle]
ORA_CONFIG=C:\WINDOWS\ORACLE.INI
SQL*Net TCP/IP for Windows
--------------------------
In addition to the steps above, there are some additional steps that need
to be performed when installing SQL*Net TCP/IP for Windows on a network
drive.
1. When setting up the file server, copy the VSL.INI along with the
ORACLE.INI from the Windows directory to the Oracle home directory
after installing SQL*Net TCP/IP for Windows on the network drive.
2. When setting up the client workstation, copy the VSL.INI along with
the ORACLE.INI from the Oracle home directory on the network drive
to the client workstation's Windows directory.
3. If the client workstation is using a different TCP/IP vendor than
what was selected during the installation, you will need to reinstall
SQL*Net TCP/IP onto the network drive and select the appropriate vendor
so that the necessary files for that vendor are installed. Follow the
steps outlined above for Setting Up the File Server and then follow the
steps for Setting Up the Client Workstations.
Advantages
----------
1. Multiple client workstations may be supported from a single copy of
the Oracle software.
2. Disk space is conserved on the client workstations since all of the
executables reside on the file server.
3. Software version maintenance is easy since only a single installation
needs to be upgraded.
Disadvantages
-------------
1. Performance might be affected because of network traffic.