SQLNet/ Documentos / Soporte Técnico / Servicios / Tilsor
 
 

SQL*NET V2 CONFIGURATION STEPS

Creation Date: 20-APR-1999
Last Revision Date: 04-APR-2000

SQL*NET V2 CONFIGURATION STEPS
==============================

This bulletin will provide a general overview of configuration steps for
SQL*Net V2.

Products to Be Installed on Both the Server and All Client Machines
====================================

* SQL*Net V2
* Protocol Specific Adapter (If you are using TCP/IP, install the
Oracle TCP/IP Adapter, etc.)
* Network Manager (Please note, that beginning with Oracle7 V7.2,
Network Manager will only be available for Windows 3.1 machines.
You will only need to install Network Manager on one Windows client
machine.)


Steps to Take for Configuration for Using SQL*Net V2
=====================================

1) Now that you have installed the products listed above, you will need to
use Network Manager to configure the two sets of files needed to use
SQL*Net V2. Please refer to GSX bulletin, Overview of Network Manager, to
assist you while using Network Manager.


These files include:

On the Server On the Client
============= =============

tnsnames.ora tnsnames.ora
sqlnet.ora sqlnet.ora
listener.ora

It is important to note that the "listener.ora" file is not needed on the
client machines. This file is accessed when starting up the V2 Listener on the
server.


Placing Created Files
=====================

2) Network Manager will ask you where you want to place the files that you
have created. You can choose any directory to which you have access. Two
subdirectories will be created under the directory that you have specified.
As an example, you specify C:\orawin\network\admin as your placement
directory. If you look under the admin directory you will see a new
directory under it (the name is specified within Network Manager by you)
That new directory will have two subdirectories under it. One of the
directories will contain the three server files: "tnsnames.ora",
"sqlnet.ora", and "listener.ora". The other directory will contain the two
client files: "tnsnames.ora" and "sqlnet.ora".


Moving the Server and Client Files
==================================

3) Once the files have been created, you must move the three
server files to the machine where your database resides. Place the files
into the following directory:

$ORACLE_HOME/network/admin

4) Now the client files need to be moved to the following directory on all
client machines:

$ORACLE_HOME/network/admin


Starting the Listener
=====================

5) For SQL*Net to accept connections on the server, a Listener must be
started. Use the following command to start the Listener:

lsnrctl start <listener name>

By default, the Listener name is LISTENER. If you use this default, you will
not need to specify <listener name> within the startup command; 'lsnrctl
start' is the command to use in this case.

If this command does not return any errors and returns a line of text
stating "command completed successfully", then you should be ready to accept
SQL*Net connections.


Testing the Configuration of SQL*Net on Server
==============================================

6) To test the configuration of SQL*Net on the server, try to execute a
loopback. A loopback uses SQL*Net to go from the server right back to
itself. To execute a loopback, first make a local SQL*Plus connection on
the server. Then, within SQL*Plus, execute the following command:

SQL> connect system/manager@<service name>

The service name is the first term in your "tnsnames.ora". This precedes
the 'DESCRIPTION =' line. You will probably not have to use the full
service name. There are two parameters in the "sqlnet.ora" file which, if
set, will automatically add domains to any connect string that you use.
These two parameters are: "names.default_domain" and "name.default_zone".

For example, if your service name in the "tnsnames.ora" files reads
'oracle.world', and the .default parameter is set to 'world' in the
"sqlnet.ora" file, then the syntax for doing a loopback would be:

SQL> connect system/manager@oracle

The two parameters in "sqlnet.ora" file will add a '.world' extension, so
it will look in the "tnsnames.ora" file for a service name called
'oracle.world'.

SQL*Net is configured correctly on your server if this command does not
return any errors and connects you to a SQL prompt.


Connecting From a Client Machine
================================

7) Try to connect from a client machine now that you have performed a
loopback. If you are connecting from desktop operating system, the format
will be slightly different from on the server. In the case that you are
using SQL*Plus to test the connection, you will need to enter text into
these three fields:

* username field
* password field
* connect string field

Using the above "tnsnames.ora" file example, the username would be 'system',
the password would be 'manager', and the connect string would be 'oracle'.

If this connects you to SQL*Plus, then SQL*Net is configured correctly on your
client machine.