Using Tnsnames.ora For Name Lookup When Cds Is Inaccessible - Oracle Database B10772-01 Administrator's Manual

Connecting Clients Outside DCE to Oracle Servers in DCE
To access the DB1 database, a user can use ORATCP to identify the appropriate
connect descriptor.
For example:
sqlplus scott/tiger@oratcp

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
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
out) the "native name" parameters from the
comment out the lines, add a pound sign (#) at the beginning of each line.
For example:
#native_names.use_native=true
#native_names.directory_path=(dce)
SQL*Net Release 2.3 and Oracle Net Services
You can use
unavailable if you have TNSNAMES listed as a value for the NAMES.DIRECTORY_
PATH parameter in the
For example:
names.directory_path=(dce, tnsnames)
This parameter enables you to list more than one names resolution method. The
methods are tried in order. In this example, DCE is attempted first. If it is
unsuccessful, TNSNAMES is tried next.
10-28 Oracle Database Advanced Security Administrator's Guide
file (in the context of native naming adapters) is to
tnsnames.ora
file for name lookup and resolution, remove (or comment
tnsnames.ora
for name lookup and resolution when DCE CDS is
tnsnames.ora
sqlnet.ora
file on the client. To
sqlnet.ora
file on the client.