11
Configuring Oracle Net Services

This chapter decribes the Oracle Net Services features for Alpha OpenVMS.

It contains the following topics:

• Core Oracle Net Services Products and Features

• Oracle Net Services Protocol Support

• Bequeath (BEQ) Protocol Support

• IPC Protocol Support

• TCP/IP Protocol Support

• Oracle Enterprise Manager

• Configuring Oracle Intelligent Agent for Oracle SNMP

  See Also: For more information on Oracle networking, refer to the Oracle9i Net Services Administrator's Guide.

Core Oracle Net Services Products and Features

This section describes core Oracle Net Services products and features.

Oracle Net Services and Utilities

This section describes the files and utilities that you can use to configure Oracle Net Services products.

Location of Oracle Net Services Configuration Files

The default directory for Oracle Net Services configuration files on Alpha OpenVMS systems is ora_root:[network.admin]

Oracle Net Services searches the following locations for configuration files in the following order:

1. For sqlnet.ora file, the current working directory from where an application is run.

2. The directory specified by the TNS_ADMIN environment variable, if set.

For each system-level configuration file, users may have a corresponding local private configuration file (stored in the user's home directory). The settings in the local file override the settings in the system-level file. The following table lists the system-level configuration files and the corresponding local configuration files:

System-Level Configuration File	Local Configuration File
sqlnet.ora	tns_admin:sqlnet.ora
tnsnames.ora	tns_admin:tnsnames.ora

Sample Configuration Files

Examples of the listener_ora.sample, names_ora.sample,
sqlnet_ora.sample and tnsnames_ora.sample configuration files are located in the $ORACLE_HOME:[network.admin] directory.

Oracle Net Services Protocol Support

Oracle Net Services release release 1 (9.0.1) on OpenVMS supports the following protocols:

• Bequeath (BEQ)

• IPC

• TCP/IP

Before installing the TCP/IP protocol support, you must install and configure the appropriate operating system software. The BEQ, and IPC protocol supports do not have any specific operating system requirements.

ADDRESS Specification

The IPC, TCP/IP and Oracle Net Services protocol supports each have a protocol-specific ADDRESS specification that is used for Oracle Net Services configuration files and for the DISPATCHERS initialization parameter in the initsid.ora file. See the ADDRESS specification heading under each protocol section in this chapter for more information on protocol-specific ADDRESS specification.

Table 11-1 shows a summary of ADDRESS specifications for each protocol.

Table 11-1 ADDRESS Specification Summary

(PROTOCOL=IPC)
(KEY=key)

(PROTOCOL=TCP) 
(HOST=hostname) 
(PORT=port)

Bequeath (BEQ) Protocol Support

The BEQ protocol support is both a communications mechanism and a process-spawning mechanism. To use the BEQ protocol support, the client and server must be on the same system. If a network service name is not specified, either directly by the user on the command line or Login screen or indirectly by an environment variable such as ORA_DFLT_HOSTSTR, then the BEQ protocol support is used. In this case, the BEQ protocol support always uses a dedicated server and the shared server model is never used. This dedicated server is started automatically by the BEQ protocol, which waits for the server process to start and attach to an existing System Global Area (SGA). If the startup of the server process is successful, the BEQ protocol support then provides inter-process communication through VMS mailboxes.

An important feature of the BEQ protocol support is that is does not require a listener for its operation. The protocol support is linked into the client tools and directly starts its own server process without outside interaction. However, you can only use the BEQ protocol support when the client program and Oracle9i are installed on the same system. The BEQ protocol support is always installed and always linked to all client tools and to the Oracle9i server.

IPC Protocol Support

The IPC protocol support is similar to the BEQ protocol support in that it can only be used when the client program and the Oracle9i server are installed on the same system. The IPC protocol support differs from the BEQ protocol support in that it can be used with Oracle Shared Server configurations. The IPC protocol support requires a listener for its operation. The IPC protocol support is always installed and always linked to all client tools and to Oracle9i.

Specifying a IPC ADDRESS

The IPC protocol support connection parameters are part of the ADDRESS keyword-value pair. The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file. You can enter the following parameters in any order:

(ADDRESS=

(PROTOCOL=IPC)
(KEY=key)

)

Table 11-2 describes the syntax for IPC protocol connections parameters.

Table 11-2 Syntax for IPC Protocol Connection Parameters  

Example 11-1 shows a sample IPC ADDRESS.

Example 11-1 IPC ADDRESS Specifying a Client

(ADDRESS=

(PROTOCOL=IPC)
(KEY=PROD)

)

TCP/IP Protocol Support

The default tnslnr port in OpenVMS is 1521.

Specifying a TCP/IP ADDRESS

The TCP/IP protocol connection parameters are part of the ADDRESS keyword-value pair. The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file. You can enter the parameters in any order:

(ADDRESS=

(PROTOCOL=TCP)
(HOST=hostname)
(PORT=port)

)

Table 11-3 describes the syntax for the TCP/IP protocol connection parameters.

Table 11-3 Syntax for TCP/IP Protocol Connection Parameters  

Example 11-2 shows a sample TCP/IP ADDRESS.

Example 11-2 TCP/IP ADDRESS Specifying a Client

(ADDRESS=

(PROTOCOL=TCP)
(HOST=MADRID)
(PORT=1521)

)

You can specify the last field by name, for example, (PORT=listener).

Oracle Enterprise Manager

Use the oratclsh executable to debug your Tcl scripts. Before executing oratclsh, set the TCL_LIBRARY environment variable to specify the
ORA_ROOT:[network.agent.tcl] directory.

Configuring Oracle Intelligent Agent for Oracle SNMP

Although Oracle Intelligent Agent does not require Simple Network Management Protocol (SNMP) to work, you can configure Oracle SNMP support before starting the Intelligent Agent. Note that all of the configuration files for the following steps are located in the ORA_ROOT:[network.snmp.peer] directory.

Configure Master Agent

In the CONFIG.master file, make the following change:

1. Search for the line beginning with MANAGER.

2. Change the value specified to the IP address or hostname of the system where you want SNMP trap messages sent.

You can also make other changes to the CONFIG.master file as documented within the file.

Configure the Encapsulator

To configure the encapsulator, perform the following steps:

1. Add the following line to the snmpd.conf file, where hostname_or_IP_address represents the local system IP address or host name:

2. If necessary, modify the port number specified in the CONFIG.encap file. The default port number is 1161.

3. If you modified the port number in step 2, change the value specified for the NEW_SNMPD_PORT variable in the start_peer script to this port number.

4. If necessary , modify the value specified for the NEW_SNMPD_PORT variable. This variable specifies the PEER encapsulator port to which the snmpd agent sends traps.

5. Assign different port numbers to the NEW_SNMPD_PORT and the NEW_TRAPD_PORT variables in the start_peer script. You can also modify the port number in the NEW_TRAPD_PORT variable.

Verify the start_peer Script

The start_peer script contains a line similar to the following, where snmpd_executable_path is the path of the snmpd executable:

SNMPD=snmpd_executable_path

Make sure that snmpd_executable_path is the location of the snmpd executable on your system.