[Contents] [Index] [Info] [Previous] [Next]

CHAPTER 2. SQL*Net Configuration with Network Manager

This chapter explains how to use Network Manager in an OpenVMS environment. It covers the following topics:

This chapter is intended as an OpenVMS-specific supplement to the Network Manager documentation. For general product information about Oracle Network Manager, please refer to the Oracle Network Manager Administrator's Guide.

Pre-Configuration Tasks

This section lists the tasks you must perform before using Network Manager.

Before You Set Up OpenVMS Clients

Before you set up your clients, you should have completed the following procedures:

For more information about OpenVMS system requirements and installation procedures, see the installation guide for your platform.

For information on loading and operating your protocol, see your network protocol installation guide.

Setting Up OpenVMS Clients

Complete the following configuration tasks for the OpenVMS clients on your network.

For instructions on performing these tasks, refer to the documentation from your networking vendor.

Starting Network Manager

Network Manager is available on Windows 3.1, Windows 95, and Windows NT only. Before using Network Manager to generate and distribute the configuration files to your OpenVMS node(s), you must first:

Using Network Manager

This section gives information about using the Network Manager.

Protocol-Specific Information

In preparing to use Network Manager, the Understanding SQL*Net guide suggests that you plan what specific information about your network you will enter. Aside from entering the names of your communities and listeners, the addresses of your servers, and system identifiers of your databases, you will need to enter protocol-specific information.

If you do not want to accept Network Manager's default values for some of these protocol-specific keywords, enter your own values using the format suggested in Table 2-1.

Protocol Keyword Value
DECnet NODE <nodename>
OBJECT <alphanumeric string>
TCP/IP HOST <hostname>
PORT <number>
Table 2-1 Protocol-specific Information
See Chapter 3, "The Protocol Adapters" for details and examples.

Location-Specific Parameters

The Network Manager window called "Oracle Database" has a field called "Location-specific parameters," with the following keyword:

PROGRAM=

After the keyword, enter the file specification of the command procedure that sets up the environment for the database and starts the database server.

The full entry should be in the following format:

PROGRAM=<directory><filename>

where:

Directory Full specification of the directory containing the command procedure. Do not use a logical name to refer to this directory.
Filename Name of the command file that sets up the database environment. A sample file, called ORASRV_NETV2_COM.SAMPLE, is in the TNS_ADMIN directory. You can use this sample file as a base, editing it so that it contains correct information about your own database.

User-Defined Parameters

This field, which is also in the Oracle Database window, asks whether there are any special parameters you wish to set.

This field is optional for configurations of Oracle7 on OpenVMS. If you wish, you can use this field to set preferences for the server process, such as process quotas and priority.

Syntax of the LISTENER.ORA File

listener_alias =
	(ADDRESS_LIST=
		  (ADDRESS=
			(PROTOCOL=TCP)
			(PORT=number)
			(HOST=name|ip_address)
			(QUEUESIZE=number))
		  (ADDRESS=
			(PROTOCOL=DECNET)
			(NODE=name)
			(OBJECT=object name|number)
			(QUEUESIZE=number)))
STOP_listener_alias=YES|NO
CONNECT_TIMEOUT_listener_alias=number
TRACE_LEVEL_listener_alias=number|USER|ADMIN|OFF
SID_LIST_listener_alias = 
		(SID_DESC=
			(SID_NAME=sid_name)
			(PROGRAM=file-spec)
			(TIMEOUT=number)			(optional)
			(OUT=file-spec)			(optional)
			(OSDS=(PRIORITY=number)		(optional)
			     (QUOTA=(ASTLM=number)		(optional)
			            (BIOLM=number)		(optional)
			            (BYTLM=number)		(optional)
			            (CPULM=number)		(optional)
			            (DIOLM=number)		(optional)
			            (FILLM=number)		(optional)
			            (PGFLQUOTA=number)	(optional)
			            (PRCLM=number)		(optional)
			            (TQELM=number)		(optional)
			            (WSQUOTA=number)	(optional)
			            (WSDEFAULT=number)	(optional)
			            (ENQLM=number)		(optional)
			            (WSEXTENT=number)	(optional)
			            (JTQUOTA=number))))	(optional)

Sample LISTENER.ORA File SID_LIST

SID_LIST_listen1= 
(SID_DESC= 
	(SID_NAME=PROD)
	(PROGRAM=DISK$NET1:[ORACLE732.DB_PROD]ORASRV_NETV2.COM)
	(TIMEOUT=24)
	(OSDS=
		 (QUOTA=
			(ASTLM=123)
			(BIOLM=56)
			(BYTLM=34567)
			(CPULM=999999)
			(DIOLM=34)
			(FILLM=89)
			(PGFLQUOTA=56789)
			(PRCLM=1)
			(TQELM=12)
			(WSQUOTA=3456)
			(WSDEFAULT=2345)
			(ENQLM=56)
			(WSEXTENT=789)
			(JTQUOTA=3))))

In this example, note the following settings:

Additional Information: If you are using an OpenVMS system to create files that will be used by another operating system, you should refer to the Oracle documentation for this operating system.

Creating Tables for Oracle Names

If you will be using Oracle Names, you must store information about your network in a database. To create the database tables for storing this configuration information, do the following:

	SQLPLUS> @tns_admin:rosbild
	SQLPLUS> @tns_admin:rosgrnt PUBLIC
	SQLPLUS> @tns_admin:nmcbild
	SQLPLUS> @tns_admin:rosgrnt PUBLIC

Creating and Distributing the Configuration Files

As described in Understanding SQL*Net, the Network Manager generates several configuration files for the Oracle networking products. Appendix A of Understanding SQL*Net describes the contents of the configuration files.

After you've generated these files using Network Manager, you must distribute them among the client and server nodes that will be using them.

The following table lists the configuration files and their appropriate directory locations. Copy each file to the location listed in Table 2-2.

Configuration File Node Directory Location
TNSNAMES.ORA Clients not using Oracle Names ORA_ROOT:[NETWORK.ADMIN]
NAMES.ORA Node on which Oracle Names is installed ORA_ROOT:[NETWORK.ADMIN]
SQLNET.ORA Clients and servers ORA_ROOT:[NETWORK.ADMIN]
LISTENER.ORA Servers ORA_ROOT:[NETWORK.ADMIN]
TNSNAV.ORA Not applicable on OpenVMS
TNSNET.ORA Not applicable on OpenVMS
INTCHG.ORA Not applicable on OpenVMS
PROTOCOL.ORA Valid node verification ORA_ROOT:[NETWORK.ADMIN]
Table 2-2 Configuration files and directory locations

If you are generating to an OpenVMS Names Server, once again, verify both the general connectivity between the PC and the OpenVMS host, as well as the connectivity between PC NetMan and your OpenVMS database.

[Contents] [Index] [Info] [Previous] [Next]