Oracle7 Administrator's Reference for UNIX

Oracle DCE Native Naming Adapter

Configuring Clients and Servers

The DCE Native Naming Adapter must be installed on all clients and servers that use CDS for name resolution and must be configured using Network Manager.

See Also: The "Entering Component Information" chapter in the Oracle Network Manager Administrator's Guide for more information about native naming.

Resolving Oracle Service Names

After installing the DCE adapter, add the following to the sqlnet.ora file:

native_names.use_native=true

native_names.directory_path=(dce)

The client's name requests will be resolved in DCE instead of by a local tnsnames.ora file.

Loading Oracle Service Names

To load the Oracle service names into DCE, perform the following steps:

tnsnames.ora

/opt/dcelocal/etc/cds_attributes

	1.3.22.1.5.1     TNS_Address     char

TNS_address object identifier

(1.3.22.1.5.1)

cds_attributes

TNS_address object identifier

1.3.22.1)

cdsadv

TNS_address object identifier

protocol.ora

	dce.tns_address_oid=1.3.22.1.x.y

Note: Verify that the TNS_Address Object Identifier value in the cds_attributes file matches the value specified in the dce.tns_address_oid parameter in the protocol.ora file.

5. To load the Oracle service names or aliases into DCE, enter:

	% dce_login cell_admin

A prompt appears asking for a password. After entering the password, enter:

	% tnnfg dceload <pathname_to_TNSNAMES.ORA>

If you configure a new service, tnnfg adds it to tnsnames.ora.

The tnsnames.ora File

The tnsnames.ora file lists Oracle service names and connect descriptors of network destinations or end points. The following DCE address shows a network address for the financials Oracle server that connects to the /.../Cell_Name/subsys/oracle/names DCE directory:

financials=(DESCRIPTION=

   (ADDRESS=

     (PROTOCOL=DCE)

     (SERVER_PRINCIPAL=oracle))

     (CELL_NAME=us.oracle.com)

     (SERVICE=financials)

   (CONNECT_DATA=

     (SID=financials))

where:

SERVICE_PRINCIPAL is mandatory for the server and optional for the client
SERVICE is mandatory for both the server and the client
SID is the Oracle system identifier. It is mandatory for both servers and clients. SID is unique for each node and is not used in DCE.

The service name's address in tnsnames.ora must match the address in listener.ora. For example, the financials service has a connect descriptor.

See Also: The Oracle7 Server Administrator's Guide and Understanding SQL*Net for information about operating system or network authentication.

Description of the DCE Address Parameters

DCE addresses in the listener.ora and tnsnames.ora configuration files are defined by DCE parameters, with the following syntax:

ADDRESS=(PROTOCOL=DCE)

   (SERVER_PRINCIPAL=server_name)

   (CELL_NAME=cell_name)

   (SERVICE=service_name))

where:

DCE is the DCE RPC protocol.
server_name is mandatory for the server and optional for the client. It is mandatory in listener.ora and specifies the principal under which the server will start. It is optional in tnsnames.ora and specifies the principal of the server to which the client must connect. If not specified one-way, authentication is used.
cell_name is an optional field that specifies the DCE cell name of the database. If this parameter is not set, the cell name defaults to the local cell (useful for single-cell environments). It is not required if the SERVICE parameter specifies the complete path to the service.
service_name is the service registered with CDS (for the server). It is used to query CDS for the location of Oracle DCE servers (for the client). The default directory to store service names in CDS is /.../Cell_Name/subsys/oracle/service_registry.

SERVICE=/.../Cell_Name/subsys/oracle/service_registry/Service_Name is one way to specify a service. A service can also be specified as SERVICE=Service_Name if CELL_NAME=Cell_Name is specified.

If you specify SERVICE=Service_Name, and CELL_NAME=Cell_Name is not specified, the cell name defaults to the local cell. (This method of specifying service names only works well in single-cell environments.)

Connecting to Oracle Servers in DCE

Clients without access to DCE and CDS can connect to Oracle servers in DCE over TCP/IP or another protocol. Clients can connect to an Oracle server only if another DCE listener is configured to connect to an Oracle server. After another listener is configured, clients can use standard Oracle and SQL*Net procedures to connect to an Oracle server in DCE.

If a client does not have access to DCE, DCE security is not available and the service name lookup uses tnsnames.ora, not the CDS name server.

SERVICE_PRINCIPAL	is mandatory for the server and optional for the client
SERVICE	is mandatory for both the server and the client
SID	is the Oracle system identifier. It is mandatory for both servers and clients. SID is unique for each node and is not used in DCE.

DCE	is the DCE RPC protocol.
server_name	is mandatory for the server and optional for the client. It is mandatory in listener.ora and specifies the principal under which the server will start. It is optional in tnsnames.ora and specifies the principal of the server to which the client must connect. If not specified one-way, authentication is used.
cell_name	is an optional field that specifies the DCE cell name of the database. If this parameter is not set, the cell name defaults to the local cell (useful for single-cell environments). It is not required if the SERVICE parameter specifies the complete path to the service.
service_name	is the service registered with CDS (for the server). It is used to query CDS for the location of Oracle DCE servers (for the client). The default directory to store service names in CDS is */.../Cell_Name/subsys/oracle/service_registry*.