6
Configuring Oracle Net8

• Supplemental Documentation
• Core Net8 Products and Features
• Oracle Net8 Protocol Adapters
• The BEQ Protocol Adapter
• The IPC Protocol Adapter
• The TCP/IP Protocol Adapter
• Net8 Naming Adapters
• Oracle Enterprise Manager (OEM) Intelligent Agent

Supplemental Documentation

See Also: The following documents provide a full discussion of Oracle Net8 features: Oracle Net8 Administrator's Guide Oracle Networking Quick Reference Card for Net8 Oracle Security Server Guide Oracle Cryptographic Toolkit Programmer's Guide

Supplementary Information in README Files

Table 6-1 shows the location of README files for various bundled products. The README files describe changes since the last release.

Table 6-1 Location of README Files for Oracle Products

Core Net8 Products and Features

See Also: Sample files can be found in the Oracle Net8 Administrator's Guide.

Net8 Files and Utilities

Location of Net8 Configuration Files

The default directory for global Oracle Net8 and Connection Manager files is /var/opt/oracle on Solaris.

Oracle Net8 and Connection Manager search for global files in the following order:

1. The directory specified by the environment variable, TNS_ADMIN, if set.
2. The /var/opt/oracle directory.
3. $ORACLE_HOME/network/admin.

If your files are not in the default directory, use the TNS_ADMIN environment variable in the startup files of all network users to specify a different location:

For the C shell, enter:

% setenv TNS_ADMIN new_default

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 private file override the settings in the system level file. The private configuration file for sqlnet.ora is $HOME/.sqlnet.ora. The private configuration file for tnsnames.ora is $HOME/.tnsnames.ora. Syntax for these files is identical to that of the corresponding system files.

Sample Configuration Files

Examples of the cman.ora, listner.ora, names.ora, sqlnet.ora, and tnsnames.ora configuration files are located in $ORACLE_HOME/network/admin/samples.

The adapters Utility

To display installed Oracle Net8 adapters, enter:

% adapters

To display adapters linked with a specific executable, enter:

% adapters executable

For example, the following command displays the adapters linked with the oracle executable:

% adapters oracle
Protocol Adapters linked with oracle are:

BEQ Protocol Adapter
IPC Protocol Adapter
TCP/IP Protocol Adapter

Net8 Naming Adapters linked with oracle are:

Oracle TNS Naming Adapter
Oracle Naming Adapter

Advanced Networking Option/Network Security products linked with oracle are:

Oracle Security Server Authentication Adapter

Oracle Connection Manager

For information on the Oracle Connection Manager see the Net8 Administrator's Guide.

Multi-Threaded Server

For information on the Multi-Threaded Server see the Oracle8 Server Concepts and Oracle8 Administrator's Guide.

Oracle Names

For information on Oracle Names see the Oracle Net8 Administrator's Guide.

Net8 Assistant

The Net8 Assistant ($ORACLE_HOME/bin/net8asst.sh) requires Java 1.1.1. When installing Net8 on Solaris, the Java Runtime Environment (JRE) version 1.1.1 is installed automatically in $ORACLE_HOME/network/jre11. When the Net8 Assistant command script is executed, the java command script supplied with JRE 1.1.1 ($ORACLE_HOME/network/jre11/bin/java) is called explicitly, regardless of other Java installations on the system.

For further information on Net8 Assistant see the Oracle Net8 Administrator's Guide.

Oracle Net8 Protocol Adapters

The supported Protocol Adapters for Net8 version 8.0.5 on LINUX are BEQ Protocol Adapter, IPC Protocol Adapter, TCP/IP Protocol Adapter.

Prior to installing the TCP/IP Net8 Protocol Adapters, the appropriate operating system software must be installed and configured. Refer to the Oracle8 Installation Guide for LINUX for requirements details. The BEQ and IPC Net8 Protocol Adapters do not have any specific operating system requirement.

The IPC, TCP/IP Net8 Protocol Adapters each have a protocol-specific ADDRESS specification that is used for Net8 configuration files and for the MTS_LISTENER_ADDRESS database initialization parameter (init.ora). See the ADDRESS specification heading under each Protocol Adapter section in this chapter for details.

Table 6-2 ADDRESS Specification Summary

(PROTOCOL = BEQ)
(PROGRAM = ORACLE_HOME/bin/oracle)
(ARGV0 = oracleORACLE_SID)
(ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
(ENVS = 'ORACLE_HOME=ORACLE_HOME,ORACLE_SID=ORACLE_SID')

(PROTOCOL=IPC)
(KEY=key)

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

The BEQ Protocol Adapter

Overview of the BEQ Protocol Adapter

The BEQ Protocol Adapter, is both a communications mechanism and a process spawning mechanism. If a service name is not specified, either directly by the user on the command line or the login screen, or indirectly through an environment variable such as TWO_TASK, then the BEQ Protocol Adapter will be used. In which case, a dedicated server will always be used, and the multi-threaded server will never be used. This dedicated server is started automatically by the BEQ Protocol Adapter, which waits for the server process to start and attach to an existing SGA. If the startup of the server process is successful, the BEQ Protocol Adapter then provides inter-process communication via UNIX pipes.

An important feature of the BEQ Protocol Adapter is that no network Listener is required for its operation, since the adapter is linked into the client tools and directly starts its own server process with no outside interaction. However, the BEQ Protocol Adapter can only be used when the client program and the Oracle8 server reside on the same machine. The BEQ Protocol Adapter is always installed, and always linked in to all client tools and to the Oracle8 server.

Specifying a BEQ ADDRESS

The BEQ Protocol Adapter connection parameters are part of the ADDRESS keyword-value pair. You can enter the parameters in any order.

(ADDRESS =

(PROTOCOL = BEQ)
(PROGRAM = ORACLE_HOME/bin/oracle)
(ARGV0 = oracleORACLE_SID)
(ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
(ENVS = 'ORACLE_HOME=ORACLE_HOME,ORACLE_SID=ORACLE_SID')

)

Syntax for BEQ Protocol Adapter connection parameters is described in Table 6-3.

Table 6-3 Syntax for BEQ Protocol Adapter Connection Parameters

Example 6-1 BEQ ADDRESS Specifying a Client

The following is an example of an BEQ ADDRESS:

(ADDRESS =

(PROTOCOL = BEQ)
(PROGRAM = /u01/app/oracle/product/8.0.5/bin/oracle)
(ARGV0 = oracleV805)
(ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
(ENVS = 'ORACLE_HOME=/u01/app/oracle/product/8.0.5,ORACLE_SID=V805')

)

The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file.

The IPC Protocol Adapter

Overview of the IPC Protocol Adapter

The IPC Protocol Adapter, is similar to the BEQ Protocol Adapter in that it can only be used when the client program and the Oracle8 server reside on the same machine. The IPC Protocol Adapter differs from the BEQ Protocol Adapter in that it can be used with dedicated server and multi-threaded server configurations. The IPC Protocol Adapter requires a network listener for its operation. The IPC Protocol Adapter is always installed, and always linked in to all client tools and to the Oracle8 server.

For the IPC Protocol Adapter, the location of the UNIX Domain Socket (IPC) file on UNIX systems changed after Oracle7 7.1. Thus, if you have Oracle7 7.1 installed on the same machine as Oracle8, and you attempt to make an IPC connection between the two instances, the connection may fail. The solution to this problem is to make a symbolic link between the directory where the IPC file used to be (/var/tmp/o) and where it now resides (/var/tmp/.oracle).

Specifying an IPC ADDRESS

The IPC Protocol Adapter connection parameters are part of the ADDRESS keyword-value pair. You can enter the parameters in any order.

(ADDRESS=

(PROTOCOL=IPC)
(KEY=key)

)

Syntax for IPC Protocol Adapter connection parameters is described in Table 6-4.

Table 6-4 Syntax for IPC Protocol Adapter Connection Parameters

Example 6-2 IPC ADDRESS Specifying a Client

The following is an example of an IPC ADDRESS:

(ADDRESS=

(PROTOCOL=IPC)
(KEY=PROD)

)

The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file.

The TCP/IP Protocol Adapter

Overview of the TCP/IP Protocol Adapter

Oracle Corporation recommends that you reserve a port for your Oracle Net8 listener in the /etc/services file of each node on the network that defines the Oracle Net8 listener port. The port is commonly 1521. The entry should list the listener name and the port number, for example:

listener     1521/tcp

where listener is the name of the listener, as defined in listener.ora.

Reserve more than one port to start more than one listener.

Specifying a TCP/IP ADDRESS

The TCP/IP Protocol Adapter connection parameters are part of the ADDRESS keyword-value pair. You can enter the three parameters in any order.

(ADDRESS=

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

)

Syntax for TCP/IP Protocol Adapter connection parameters is described in Table 6-5.

Table 6-5 Syntax for TCP/IP Protocol Adapter Connection Parameters

Example 6-3 TCP/IP ADDRESS Specifying a Client

Following is an example of the TCP/IP ADDRESS specifying a client on the MADRID host:

(ADDRESS=

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

)

The last field could be specified by name, for example, (PORT=listener). The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file.

Net8 Naming Adapters

NIS Naming Adapter

For details on configuring the NIS Naming Adapter, see the Oracle Net8 Administrator's Guide, Release 8.0.

Oracle Enterprise Manager (OEM) Intelligent Agent

Agent Service Discovery and Auto-Configuration

See Also: The Oracle Enterprise Manager Configuration Guide.

Debugging Tcl Scripts

The executable oratclsh is provided for debugging your Tcl scripts. Before executing oratclsh, set the environment variable TCL_LIBRARY to point to $ORACLE_HOME/network/agent/tcl.