10
Configuring Oracle DC E Integration

• Step 1: Enable CDS for use in Performing Name Lookup
• Step 2: Modify the CDS Attributes File and Restart the CDS
• Step 3: Create a tnsnames.ora File for Loading Oracle Connect Descriptors into CDS
• Step 4: Load Oracle Connect Descriptors into CDS
• Step 5: Delete or Rename the tnsnames.ora File
• Step 6: Modify the sqlnet.ora File to Resolve Names in CDS

  ---

  Note:

  Upon completion of this task, you ca n connect to an Oracle database in your DCE environment.

  ---

Step 1: Enable CDS for use in Performing Name Lookup

To use CDS for name resolution, the DCE Integration CDS N aming Adapter must be installed on all clients and servers that use CDS. Also, the CDS namespace must have been configured for use by DCE Integration.

For example, a service name such as ORADCE and its network address can be stored in DC E CDS.

Users can typically connect to Oracle services using the familiar Oracle servi ce name if there are no domains or the database is in the user's default domain, as in the following example:

sqlplus /@ORADCE

This example assumes that DCE externally-authenticated accounts are in use.

As an alternative name resolution service, us e a local naming configuration file, tnsnames.ora, when CDS is inaccessible. To do so, locate names and addresses of all Oracle servers in the local tnsnames.ora file.

Step 2: Modify the CDS Attributes File and Restart the CDS

On all DCE machines where CDS naming is used, add the object ID for the CDS attribute TNS_A ddress to the CDS attributes file. (The object ID must be the same across all machines.)

1. Add a line in the following format to the /opt/dcelocal/etc/cds_attributes fi le:

   1.3.22.1.5.1    TNS_Address    char
   
   

   The first four digits of this TNS_Address attribute value, 1.3.22.1.x.y, are fixed, under DCE naming conv entions. If the default TNS_Address object ID value 1.3.22.1.5.1 already exists in the cds_attributes file, you must spe cify a value for the object ID that is not already in use.

   If you are unable to use the def ault value for the object ID, then you must specify the object ID in the protocol.ora file on the client.

   If you had to specify a value other than the default value 1.3.22.1.5.1, then you must add t he following parameter to the protocol.ora file:

   DCE.TNS_ADDRESS_OID=1.3.22.
   1.x.y
   
   

   Make sure that the object ID value in the cds_attributes fi le matches the value specified in the DCE.TNS_ADDRESS_OID parameter in the protocol.ora file.

2. Restart CDS on the system.

   The com mand to restart CDS varies between different operating systems. On the Solaris platform, for example, you can use the following comma nd to restart CDS:

   /opt/dcelocal/etc/rc.dce restart
   
   

Step 3: Create a tnsnames.ora Fi le for Loading Oracle Connect Descriptors into CDS

To load the Oracle service names and addresses into CDS, create or modify a local naming configuration file, tnsnames.ora. This file is used to map ser vice names to addresses for use by Oracle Net.

This section describes the parameters that mu st be included in the tnsnames.ora file. The file contains a list of Oracle service names mapped to connect descriptors of destinations or endpoints in the network. The sample DCE address in the following section shows a network address for an Oracle se rver with the Oracle service name ORADCE. It is used to connect to the service registered as DCE_SVC in the CDS directory

 /.../cell_name/subsys/oracle/names.
ORADCE=(DESCRIPT
ION=(ADDRESS=(PROTOCOL=DCE)(SERVER_PRINCIPAL=oracle)(CELL_
NAME=cell1)(SERVICE=DCE_SVC))(CONNECT_DATA=(SID=ORASID)))

Step 4: Load Oracle Connect Descriptors into CDS

To load the Oracle service names or aliases from tnsnames.ora into CDS, enter the fol lowing at the system prompt:

% dce_login cell_admin
% tnnfg dceload
full_pathname_to_tnsnames.ora
% Enter Password:(password will not display)

Be sure to enter the full path name of the tnsnames.ora file, and ensure that the s qlnet.ora file exists in the same directory as the tnsnames.ora file.

Step 5: Delete or Rename the tnsnames.ora File

You can keep tnsnames.ora available a s a backup in case CDS becomes unavailable. To assure that CDS is routinely searched instead of tnsnames.ora, configure the NAMES.DIRECTORY_PATH parameter in a profile (sqlnet.ora), as described by "Step 6: Modify the sqlnet.ora File to Resolve Names in CDS" (the next section).

Step 6: Modify the sqlnet.ora File to Resolve Names in CDS

The parameters required in a profile (sqlnet.ora) de pend upon the version of SQL*Net or Oracle Net Services you are using.

For a client or serve r to use DCE CDS Naming, the administrator must do the following:

1. Ensure that the CDS Naming Adapter has been installed on that node.
2. Add the following parameter to the sqlnet.ora file:

   NAMES.DIREC
   TORY_PATH=(cds, tnsnames, onames)
   
   

   The first name resolution servi ce listed as a value for this parameter is used. If it is unavailable for any reason, the next name resolution service is used, and s o forth.

Connecting to an Oracle Database Server in the DCE Environment

This section describes how to connect to an Oracle database after installing Oracle DCE Integration, and configuring both DCE a nd Oracle to use Oracle DCE Integration in the following topics:

• < /a>Starting the Listener
• Connecting to an Oracle Database by Using DCE Authentication for Single Sign-On
• Connecting to an Oracle Database by Using Password Authentication

Starting the Li stener

To start the listener, do the following:

1. Enter the following commands:

   <
   /a>% dce_login principal_name password 
   % lsnrctl start listener_name
   
   

   For example, if the listener name is LSNR_DCE in the listener.ora file, enter the following:

   % dce_login oracle orapwd
   % lsnrctl start LSNR_DCE
   
   

2. Verify that the server has registered its binding handler with rpcd: < pre class="CE1"> % rpccp show mapping

   Look for the line that includes the dce_service_name that is part of the listener address.

3. Verify that the service has been created by searching for the dce_service_name as follows:

   % cdscp show object "/.:/subsys/oracle/service_registry/dce_servi
   ce_name"
   
   

   For example:

   The following command shows you the mapping in the CDS namespace that the listener has chosen for the en dpoint:

   % cdscp show object "/.:/subsys/oracle/service_registry/dce_svc"
   
               SHOW
             OBJECT    /.../subsys/oracle/service_registry/dce_svc
   <
   a name="1007968">              AT   1999-05-15-17:10:52
   RPC_ClassVersion = 0100
   
       CDS_CTS = 1999-05-16-00:05:01.221106100/aa-00-04-00-3e-8c           
            CDS_UTS = 1999-05-16-00:05:01
   .443343100/aa-00-04-00-3e-8c                  
          CDS_Class = RPC_Server
   CDS_ClassVer
   sion = 1.0
         CDS_Towers = :
              Tower = ncacn_ip_tcp:144.25.23.57[]
   

Connec ting to an Oracle Database by Using DCE Authentication for Single Sign-On

After externally-identified accounts have been set up, you can take advantage of DCE authentication to log in to Oracle without providing any username or password information. To use this single sign-on capability, just log in to DCE using a command like the fo llowing:

% dce_login principal_name password

For example:

% dce_login oracle orapwd

You can now connect to an Oracle server without using a username or password. Enter a command like the following:

% sqlplus /@net
_service_name

where net_service_name is th e database service name.

For example:

% sqlplus /@ORADCE

Connecting to an Oracle Database by Using Password Authentication

From a client, you can still connect with a user name and password:

% sqlplus username/password@net_service_name

where net_service_name is the Oracle Net service name.

For e xample:

% sqlplus scott/tiger@ORADCE

Connecting Clients Outside DCE to Oracle Servers i n DCE

Clients without access to DCE and CDS can still connect to Orac le servers in DCE using TCP/IP or some other protocol if a listener is configured to do this. If a listener has been configured in th e listener.ora file on the server, non-DCE clients can use normal Oracle Database and Oracle Net Services procedures to connect to an Oracle server in DCE.

The following section contains these topics, which include samples of listener.ora and tnsnames.ora files as they would be configured if a client from outside of DCE wanted to connect to Oracle database servers in a DCE environment:

• Sample Paramet er Files
• Using tnsnames.ora for Name Lookup When CDS Is Inaccessible

Sample Parameter Files

At least the follo wing two Oracle parameter files are needed for successful client/server communications; create and modify these files using a text ed itor:

The parameter files are described in the following sections:

• The listener.ora File
• The tnsnames.ora File

The listener.ora File

The listener.ora file resides on the listener node. It defines listener characteristics and the addr esses at which the listener listens.

In the following example, each element is displayed on a separate line, to show the file's structure. This is the recommended format, but you do not have to put each element on a separate line. Be sure to include all the appropriate parentheses, and to indent if you must continue an element on the next line.

This example assumes the UNIX operating system and the TCP/IP protocol for one listener, and the DCE pr otocol for another listener. A single listener can have multiple addresses. For example, instead of having two separate listeners for different database instances on a server node, you could have one listener for both, listening on both TCP/I P and on DCE. However, performance is improved with separate listeners.

LSNR_TCP=
   (ADDRESS_LIST=
       (ADDRESS=
              (PROTOCOL=IPC)
              (KEY=DB1)
       )
       (ADDRESS=

        (PROTOCOL=tcp)
              (HOST=rose)
              (PORT=1521)
       ))
SID_LIST_LSNR_TCP=
      (SID_DESC=
             (SID_NAME=ORASID)
             (ORACLE_HOME=/usr/jprod/Oracle Database)
      )
LSNR_DCE=
(ADDRESS=
  (PROTOCOL=DCE)
  (SERVER_PRINCIPAL=oracle)
  (CELL_NAME=cell1)
  (SERVICE=dce_svc))
SID_LIST_LSNR_DCE=
  (SID_DESC=
    (SID_NAME=ORASID)
    (O
RACLE_HOME=/usr/prod/oracle8))
#For all listeners, the following parameters list sample
#
default values.
PASSWORDS_LISTENER=
STARTUP_WAIT_TIME_LISTENER=0
CONNECT_TIMEOUT_LISTENER=10
TRACE_LEVEL_LISTENER=OFF
TRACE_DIRECTORY_
LISTENER=/usr/prod/Oracle Database/network/trace
TRACE File_LISTENER=listener.trc
LOG_DIR
ECTORY_LISTENER=/usr/prod/Oracle Database/network/log
LOG_FILE_LISTENER=listener.log

The tnsnames.ora File

This file resides on both the client and the server nodes. It lists the service names and addresses of all services on the network.

The following sample tnsnames.ora file maps the service name ORATCP to the connect descriptor that includes a TCP/IP address and the service name ORADCE< /code> to a connect descriptor that includes a DCE address.

ORATCP = (DESCRIPTION=
       (ADDRESS=
         (PROTOCOL=TCP)
         (HOST=rose)
         (PORT=1521)
        )
        (CONNECT_DATA=

       (SID=DB1)
        )
       )
ORADCE=(DESCRIPTION=
      (ADDRESS=
        (PROTOCOL=DCE)
        (SERVER_PRINCIPAL=oracle)
        (CELL_NAME=cell1)
        (SERVICE=dce_svc)
       )
       (CONNECT_DATA=
              (SID=ORASID)
       )
<
/a>       )

To access the DB1 database, a user can use ORATC P to identify the appropriate connect descriptor.

For example:

sqlplus scott/tiger@oratcp

< h3 class="H2">Using tnsnames.ora for Name Lookup When CDS Is Inaccessible

Typically, names are resolved into network addresses by CDS. Although the main purpose of the tnsnames.ora file (in the context of native naming adapters) is to load Oracle service names and network addresses into CDS, it could be used temporarily as a backup name resolution service if CDS is inaccessible.

SQL*Net Release 2.2 and Earlier

To use the tnsnames.ora file for name lookup and resolution, remove (or comment out) the "native name" parameters from the sqlnet.ora file on the client. To comment out the lines, add a pound sign (#) at the beginning of each line.

For exa mple:

#native_names.use_native=true
#native_names.directory
_path=(dce)

SQL*Net Release 2.3 and Oracle Net Services

You can use t nsnames.ora for name lookup and resolution when DCE CDS is unavailable if you have TNSNAMES listed as a value for the NAMES.DIRECTORY_PATH parameter in the sqlnet.ora file on the client.

For example:

names.directory_path=(dce, tnsnames)

<
a name="1007453">

This parameter enables you to list more than one names resolution m ethod. The methods are tried in order. In this example, DCE is attempted first. If it is unsuccessful, TNSNAMES is tried next.

---

Note: In this case, DCE security is not available to clients. Also, service names are resolved to ne twork addresses and located in a tnsnames.ora file on the client, not using the CDS name server.

Previous Next

Copyright © 1996, 2 003 Oracle Corporation All Rights Reserved.

Home Book List Contents Index Master Index Feedback < /td>