Oracle7 Administrator's Reference for UNIX

Oracle DECnet Protocol Adapter

DECnet is a network protocol developed by Digital Equipment Corporation (DEC) to network its hardware. A node is a system on a DECnet network capable of processing, sending, and receiving information, such as:

VMS or UNIX minicomputers

IBM or compatible mainframes

network terminal servers

desktop computers running DEC PathWORKS for MS-DOS, DEC PathWORKS for OS/2, or DEC PathWORKS for Macintosh

Nodes are classified as either end nodes or routing nodes. End nodes act only as end points in a process-to-process communication. Routing nodes connect networks and perform dynamic cost-based routing. Each node is identified by a unique network address and is assigned a node name or alias.

Using the Oracle DECnet Protocol Adapter

Specifying the DECnet ADDRESS

The Oracle DECnet Protocol Adapter allows TNS and its applications to communicate over the DECnet communications protocol. The DECnet adapter implements a standard interface resolve the equivalent communication functions of the DECnet protocol and TNS.

After the DECnet protocol and Oracle DECnet Protocol Adapter are installed use the DECnet parameters in the TNS connect descriptors to identify nodes in the DECnet community.

The DECnet adapter parameters are part of ADDRESS keyword-value pairs. You can enter the DECnet community name and the six DECnet parameters in any order in the ADDRESS construct. The syntax is:

(ADDRESS=

   [(COMMUNITY=community_name)]

   (PROTOCOL=DECNET)

   (NODE=node)

   (OBJECT=object_id)

   [(USER=operating_system_username)]

   [(PASSWORD=operating_system_password)]

   [(ACCOUNTING=accounting_code)]

where:

community_name is the community name to use with MPI. The community name should be unique on the network.
PROTOCOL is the protocol adapter. The value can be uppercase or lowercase. For DECnet, the value is DECNET.
node is the name or number of the remote node you want to connect to. The node must be included in the list of node names and node numbers defined in the interactive Network Control Program (NCP). NCP allows up to six characters for a node name.
object_id is the name or number of the object (or the remote node) you want to connect to. An object name can be up to six characters. An object number must be 256 or less and has the following syntax:
\#object_number
Because the pound sign (#) is a reserved character in TNS, it is preceded by a backslash (\).
operating_system_ username is the optional user name on the target node if you use a DECnet listener on the remote node.
operating_system_ password is the optional user password on the target node if you use a DECnet listener on the remote node.
accounting_code is the optional business accounting code used for CPU tracking and billing if you use a DECnet listener on the remote node.

Example:

The following example is a DECnet ADDRESS with client MADRID in the C1.SALES.ACME community with remote a listener object LSNR:

(ADDRESS=

   (COMMUNITY=C1.SALES.ACME)

   (PROTOCOL=DECNET)

   (NODE=MADRID)

   (OBJECT=LSNR))

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

MTS Configuration

To enable the MTS configuration, update the initsid.ora and listener.ora files to specify the dispatchers to be used for each Oracle Protocol Adapter, then start your oracle instance.

Updating the initsid.ora File

To enable MTS, specify the following parameters in the initsid.ora file:

mts_dispatchers is the number of dispatchers. The syntax is "p,n" where p is the protocol for the dispatcher and n is the number of dispatchers to start for the protocol.
mts_max_ dispatchers is the maximum number of dispatchers.
mts_service is the dispatcher service name passed to the network listener when the dispatcher starts. This service name is used by the set instance command to route users to dispatchers of a service.
mts_servers is the minimum number of shared servers.
mts_max_servers is the maximum number of shared servers.
mts_listener_ address is a SQL*Net address used to connect to the network listener. It begins with (ADDRESS=...).

Following is an example of an initsid.ora MTS dispatcher configuration:

mts_dispatchers="decnet,1"  # run 1 DECnet dispatcher

mts_max_dispatchers = 10    # max no of dispatchers

mts_service = ORA7          # dispatcher service name

                            # (=ORACLE_SID)

mts_servers = 1             # min no of shared servers

mts_servers = 10            # max no of shared servers

mts_listener_address = "(ADDRESS=(PROTOCOL=decnet)

                        (NODE=23.22)

                        (OBJECT=HELPME))"

Updating the listener.ora file

When configuring your system for MTS, specify in the listener.ora file the listener address definition for each adapter you add to initsid.ora.

community_name	is the community name to use with MPI. The community name should be unique on the network.
PROTOCOL	is the protocol adapter. The value can be uppercase or lowercase. For DECnet, the value is DECNET.
node	is the name or number of the remote node you want to connect to. The node must be included in the list of node names and node numbers defined in the interactive Network Control Program (NCP). NCP allows up to six characters for a node name.
object_id	is the name or number of the object (or the remote node) you want to connect to. An object name can be up to six characters. An object number must be 256 or less and has the following syntax:
	\#object_number
	Because the pound sign (#) is a reserved character in TNS, it is preceded by a backslash (\).
operating_system_ username	is the optional user name on the target node if you use a DECnet listener on the remote node.
operating_system_ password	is the optional user password on the target node if you use a DECnet listener on the remote node.
accounting_code	is the optional business accounting code used for CPU tracking and billing if you use a DECnet listener on the remote node.

mts_dispatchers	is the number of dispatchers. The syntax is "p,n" where p is the protocol for the dispatcher and n is the number of dispatchers to start for the protocol.
mts_max_ dispatchers	is the maximum number of dispatchers.
mts_service	is the dispatcher service name passed to the network listener when the dispatcher starts. This service name is used by the set instance command to route users to dispatchers of a service.
mts_servers	is the minimum number of shared servers.
mts_max_servers	is the maximum number of shared servers.
mts_listener_ address	is a SQL*Net address used to connect to the network listener. It begins with (ADDRESS=...).