User's Manual

Configuring Oracle Database and Oracle Net Services for Oracle DCE Integration
10-20 Oracle Database Advanced Security Administrator's Guide
For example, a service name such as ORADCE and its network address can be stored
in DCE CDS.
Users can typically connect to Oracle services using the familiar Oracle service
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, use 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_Address 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
file:
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 conventions. If the default TNS_Address object ID
value 1.3.22.1.5.1 already exists in the cds_attributes file, you must
specify a value for the object ID that is not already in use.
If you are unable to use the default 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 the 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 file matches the value
specified in the DCE.TNS_ADDRESS_OID parameter in the protocol.ora file.
See Also: DCE Integration installation instructions, and "Task 3:
Configure DCE CDS for Use by Oracle DCE Integration" on
page 10-6.