The Easy Connect naming method eliminates the need for service name lookup in the tnsnames.ora files for TCP/IP environments. In fact, no naming or directory system is required when using this method.

This naming method provides out-of-the-box TCP/IP connectivity to databases. It extends the functionality of the host naming method by enabling clients to connect to a database server with an optional port and service name in addition to the host name of the database:

CONNECT username@[//]host[:port][/[service_name][:server_type][/instance_name]]
Enter password: password

The connect identifier converts to the following connect descriptor:

(DESCRIPTION= 
  (ADDRESS=(PROTOCOL=tcp)(HOST=host)(PORT=port))
  (CONNECT_DATA=
    (SERVICE_NAME=service_name)
    (SERVER=server_type)
    (INSTANCE_NAME=instance_name)))

If the Oracle Database server installation was performed in Typical mode, then the default service name used by the Oracle instance is the database name, and the following Easy Connect syntax can be used to connect to that instance:

SQLPLUS /nolog
SQL> CONNECT username@host/db_name
SQL> Enter password: password

Table 8-1 lists the Easy Connect syntax elements and descriptions for each.

scott@//sales-server
Enter password: password

SQL> CONNECT scott@sales-server

SQL> CONNECT scott@//sales-server

The connect strings in Example 8-1 connect the client to database service sales.us.example.com with a listening endpoint of 1521 on database server sales-server.

CONNECT scott@sales-server:1521/sales.us.example.com
CONNECT scott@//sales-server/sales.us.example.com
CONNECT scott@//sales-server.us.example.com/sales.us.example.com

After each of the connect strings in Example 8-1, you must enter a password to connect to the database service.

The connect strings in Example 8-1 convert into the following connect descriptor:

(DESCRIPTION= 
  (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521))
  (CONNECT_DATA=
    (SERVICE_NAME=sales.us.example.com)))

• About Easy Connect Plus
  Starting with Oracle Database 19c release, the Easy Connect syntax that applications use to connect to Oracle Database has improved functionality. The new version is called Easy Connect Plus.
• Examples of Easy Connect Naming Method
  
• Configuring Easy Connect Naming on the Client
  
• Configuring Easy Connect Naming to Use a DNS Alias
  

The local naming method adds network service names to the tnsnames.ora file. Each network service name maps to a connect descriptor.

Example 8-2 shows the network service name sales mapped to the connect descriptor contained in DESCRIPTION. The DESCRIPTION section contains the protocol address and identifies the destination database service. In this example, the protocol is TCP/IP and the port is 1521.

sales=
(DESCRIPTION= 
  (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521))
  (CONNECT_DATA= 
     (SERVICE_NAME=sales.us.example.com)))

Example 8-3 shows a valid tnsnames.ora entry to connect to a host identified with an IPv6 address and a port number of 1522.

salesdb =
  ( DESCRIPTION =
    ( ADDRESS=(PROTOCOL=tcp)(HOST=2001:0db8:1:1::200C:417A)(PORT=1522) )
    ( CONNECT_DATA = 
        (SERVICES_NAME=sales.example.com) )
  )

You can configure local naming during or after installation, as described in the following sections:

• Configuring the tnsnames.ora File During Installation
  
• Configuring the tnsnames.ora File After Installation
  

With the directory naming method, connect identifiers are mapped to connect descriptors contained in an LDAP-compliant directory server, such as Oracle Internet Directory and Microsoft Active Directory. A directory provides central administration of database services and network service names, making it easier to add or relocate services.

A database service entry is created during installation. Oracle Enterprise Manager Cloud Control and Oracle Net Manager are used to create and modify network service names and network service alias entries, and to modify the database service entry. Clients can use these entries to connect to the database.

To configure the directory naming method, perform the following tasks:

Task 1   Verify Directory Compatibility

On the computer from which you plan to create network service names, do the following verification steps:

1. Ensure the computer has the latest release of Oracle Net Services software. The release information is located in the About Net Manager option on the help menu.

2. Run Oracle Internet Directory Configuration Assistant to verify directory server, Oracle Context, and Oracle schema releases.

   See Also:

   Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory for additional information about configuring directory server usage

Task 2   Create Net Service Names in the Directory

You can configure clients to use a network service name rather than the database service entry. The following procedure describes how to create network service names:

Note:

• Only users that are members of either the OracleNetAdmins or OracleContextAdmins group can create network service name entries in a directory. To add or remove users from the OracleNetAdmins group, see "Who Can Add or Modify Entries in the Directory Server".

• You can export existing network service names from a tnsnames.ora file. See "Exporting Local Naming Entries to a Directory Naming Server".

1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

   See Also:

   "Accessing the Net Services Administration Page"

2. Select Directory Naming from the Administer list, and then select the Oracle home that contains the location of the directory server.

3. Click Go.

   The Directory Naming page appears.

4. Click the Net Service Names tab.

5. In the Results section, click Create.

   The Create Net Service Name page with the General tab appears.

6. Enter a name in the Net Service Name field.

7. In the Database Information section, configure service support, as follows:

   1. Enter a destination service name.

      If the destination service name is for an Oracle9i database or later, then select Use Service Name, and enter a service name in the Service Name field.

      See Also:

      "About Connect Descriptors" for additional information about the service name string to use

   2. Select a database connection type. Oracle recommends that you use the Database Default for the connection type. If a shared server is configured in the initialization parameter file, then the following options are available:

      • Select Dedicated Server to force the listener to spawn a dedicated server, and bypass shared server configuration.

      • Select Shared Server to guarantee the connection always uses shared server.

      See Also:

      Configuring a Shared Server Architecture for additional information about shared server configuration

8. In the Addresses section, configure protocol support, as follows:

   1. Click Add.

      The Add Address page appears.

   2. From the Protocol list, select the protocol that the listener is configured to listen. This protocol must also be installed on the client.

   3. Enter the appropriate parameter information for the selected protocol in the fields provided.

      See Also:

      Oracle Database Net Services Reference for additional information about protocol parameter settings

   4. (Optional) In the Advanced Parameters section, specify the I/O buffer space limit for send and receive operations of sessions in the Total Send Buffer Size and Total Receive Buffer Size fields.

      See Also:

      "Configuring I/O Buffer Space " for additional information

   5. Click OK.

      The protocol address is added to the Addresses section.

9. Click OK to add the network service name.

   The network service name is added to the Results section of the Net Service Names tab.

   See Also:

   • "Creating a List of Listener Protocol Addresses" to configure multiple protocol addresses

   • "About the Advanced Connect Data Parameters" to configure additional CONNECT_DATA options

Task 3   Modify Connectivity Information for Database Service Entries

When database registration with the directory naming completes, a database service entry is created in the directory. By default, this entry contains network route information with the location of the listener through a protocol address. You can re-create this information or modify the existing network route information.

Note:

Only users that are members of the OracleNetAdmins or OracleContextAdmins group can modify network information for a database service in a directory. To add or remove users from these groups, see "Who Can Add or Modify Entries in the Directory Server".

The following procedure describes how to create or modify network route information for a database service:

1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

   See Also:

   "Accessing the Net Services Administration Page"

2. Select Directory Naming from the Administer list, and then select the Oracle home that contains the location of the directory server.

3. Click Go. You may be prompted to log in to the database server and the directory server.

   The Directory Naming page appears.

4. Click the Database Services tab.

5. In the Simple Search section, select Oracle Context and search criteria to see the network service names for Oracle Context.

   The database service names display in the Results section.

6. In the Results section, select a database service, and then click Edit.

Task 4   Create Net Services Aliases

Net service aliases in a directory server enable clients to refer to a database service or a network service name by an alternative name. For example, a network service alias of salesalias can be created for a network service name of sales. When salesalias is used to connect to a database, as in CONNECT scott@salesalias, it resolves to and use the connect descriptor information for sales.

There are two main uses of network service aliases:

• Use a network service alias as a way for clients to refer to a database service or network service name by another name.

• Use a network service alias in one Oracle Context for a database service or network service name in a different Oracle Context. This enables a database service or network service name to be defined once in the directory server, and referred to by clients that use other Oracle Contexts.

  See Also:

  "Understanding Net Service Alias Entries" for an overview of network service aliases

Note:

• Only users that are members of either the OracleNetAdmins or OracleContextAdmins group can create or modify network service alias entries in a directory. To add or remove users from the OracleNetAdmins group, see "Who Can Add or Modify Entries in the Directory Server".

• To create or access network service aliases, ensure that the Oracle home is at least release 9.2.0.4.

• Net service aliases are not supported by Microsoft Active Directory.

• Ensure the NLS_LANG environment variable is set for the clients when using network service aliases.

To create a network service alias, use one of the following methods:

• Network Service Alias Configuration using Oracle Enterprise Manager Cloud Control

• Network Service Alias Configuration using Oracle Net Manager

Each method provides similar functionality.

Network Service Alias Configuration using Oracle Enterprise Manager Cloud Control

The following procedure describes how to configure a network service alias using Oracle Enterprise Manager Cloud Control:

1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

   See Also:

   "Accessing the Net Services Administration Page"

2. Select Directory Naming from the Administer list, and then select the Oracle home that contains the location of the directory server.

3. Click Go.

   The Directory Naming page appears.

4. Click the Net Service Aliases tab.

5. In the Results section, click Create.

   The Create Net Service Alias page appears.

6. Enter a name for the alias in the Net Service Alias Name field.

7. In the Referenced Service Detail section, enter the following information in the fields:

   • Oracle Context: Select the Oracle Context of the database service or network service name from the list or enter one in the field.

   • Referenced Service Name: Select the DN of the database service or network service name.

8. Click OK to add the network service alias.

   The network service alias is added to the Directory Naming page.

Network Service Alias Configuration using Oracle Net Manager

The following procedure describes how to configure a network service alias using Oracle Net Manager:

1. Start Oracle Net Manager.

   See Also:

   "Using Oracle Net Manager to Configure Oracle Net Services"

2. In the navigator pane, select Service Naming from Directory.

3. Select Aliases.

4. Select Create from the Edit menu.

5. Enter the network service alias in the Net Service Alias field.

6. Select Oracle Context and name.

7. Click Create.

8. Select Save Network Configuration from the File menu.

Task 5   Configure LDAP as the First Naming Method for Client Lookups

Configure directory naming as the first method to be used in the NAMES.DIRECTORY_PATH parameter in the sqlnet.ora file. This parameter specifies the order of naming methods Oracle Net uses to resolve connect identifiers to connect descriptors. To configure LDAP as the first naming method you can use one of the following methods:

• LDAP Configuration using Oracle Enterprise Manager Cloud Control

• LDAP Configuration using Oracle Net Manager

LDAP Configuration using Oracle Enterprise Manager Cloud Control

The following procedure describes how to specify directory naming as the first naming method using Oracle Enterprise Manager Cloud Control:

1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

   See Also:

   "Accessing the Net Services Administration Page"

2. Select Network Profile from the Administer list.

3. Click Go.

4. Select Naming Methods.

5. Select LDAP from the Available Methods list.

6. Click Move to move the selection to the Selected Methods list.

7. Use the Promote button to move LDAP to the top of the list.

8. Click OK.

LDAP Configuration using Oracle Net Manager

The following procedure describes how to specify directory naming as the first naming method using Oracle Net Manager:

1. Start Oracle Net Manager.

   See Also:

   "Using Oracle Net Manager to Configure Oracle Net Services"

2. In the navigator pane, select Profile from the Local menu.

3. From the list in the right pane, select Naming.

4. Click the Methods tab.

5. From the Available Methods list, select LDAP, and then click the right-arrow button.

6. From the Selected Methods list, select LDAP, and then use the Promote button to move the selection to the top of the list.

7. Select Save Network Configuration from the File menu.

   The sqlnet.ora file updates with the NAMES.DIRECTORY_PATH parameter, listing ldap first, such as the following:

   NAMES.DIRECTORY_PATH=(ldap, tnsnames, hostname)

Task 6   Configure the Listener

Ensure that the listener located on the server is configured to listen on the same protocol address configured for the network service name. By default, the listener is configured to listen on the TCP/IP protocol, port 1521.

See Also:

Configuring and Administering Oracle Net Listener for listener configuration details

Task 7   Connect to the Database

Clients that are configured with a default directory entry that matches the directory location of the database service or network service name can connect to the database using the following syntax:

CONNECT username@connect_identifier

Clients that are configured with a default directory entry that does not match the entry's directory location must use the entry's distinguished name or its fully-qualified name.

See Also:

• "Connect Identifier and Connect Descriptor Syntax Characteristics" for connect identifier syntax rules

• "Understanding the Directory Information Tree" for fully-qualified name usage

If you want clients to use discovery in directories which have more than one Oracle Context, then you can define the orclCommonContextMap attribute in the base admin context. This attribute overrides the orclDefaultSubscriber attribute. During name lookup the discovery operation returns both values, and the client decides based on these which Oracle Context to use.

If the orclCommonContextMap attribute is not defined, then the orclDefaultSubscriber is used as the default. If orclCommonContextMap is defined, then the client finds the default Oracle Context which is associated with its DNS domain in the orclCommonContextMap. To enable multiple default contexts, define the orclCommonContextMap with a list of associations between a domain and a DN to be used as the default oracleContext. A sample LDIF file entry is shown here:

$ ldapmodify -v -h sales-server -p 1389 -D cn=orcladmin -q
 dn: cn=Common,cn=Products,cn=OracleContext
 replace: orclCommonContextMap
 orclCommonContextMap:
 (contextMap=
   (domain_map=(domain=us.example.com)(DN="dc=example,dc=com"))
   (domain_map=(domain=uk.example.com)(DN="dc=sales,dc=com"))
  )
  

The contextMap entry must be entered without line breaks.

If a tnsnames.ora file already exists, then its network service names can be exported to a directory server. The export procedure is performed for one domain at a time.

This section explains how to export data stored in a tnsnames.ora file to a directory server. It includes the following tasks:

• Task 1, "Create Structure in the Directory Server"

• Task 2, "Create Oracle Contexts"

• Task 3, "Configure Directory Server Usage"

• Task 4, "Export Objects to a Directory Server"

Task 1   Create Structure in the Directory Server

In the directory server, create the directory information tree (DIT) with the structure in which you want to import network service names. Create the structure leading to the top of the Oracle Context.

For example, if the tnsnames.ora file supports a domain structure example.com and you want to replicate this domain in the directory, then create domain component entries of dc=com and dc=example in the directory, as shown in the following figure.

Figure 8-1 example.com in Directory Server

Description of "Figure 8-1 example.com in Directory Server"

You can replicate the domain structure you currently use with tnsnames.ora, or you can develop an entirely different structure. Introducing an entirely different structure can change the way clients enter the network service name in the connect string. Oracle recommends considering relative and fully-qualified naming issues before changing the structure.

See Also:

• Directory server vendor documentation for directory entry configuration instructions

• "Client Connections Using Directory Naming"

Task 2   Create Oracle Contexts

Create an Oracle Context under each DIT location that you created in Task 1 using Oracle Internet Directory Configuration Assistant. Oracle Context has a relative distinguished name (RDN) of cn=OracleContext. Oracle Context stores network object entries, as well as other entries for other Oracle components. In the following figure, cn=OracleContext is created under dc=example,dc=com.

Figure 8-2 Oracle Context

Description of "Figure 8-2 Oracle Context"

See Also:

• Managing Network Address Information for additional information about Oracle Context

• Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory for instructions on creating an Oracle Context

Task 3   Configure Directory Server Usage

If not done as a part of creating Oracle Contexts, then configure the Oracle home for directory server use. The Oracle home you configure should be the one that performs the export.

See Also:

Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory for additional information about configuring directory server usage

Task 4   Export Objects to a Directory Server

To export network service names contained in a tnsnames.ora file to a directory, use either Oracle Enterprise Manager Cloud Controlr or Oracle Net Manager.

• Export Objects using Oracle Enterprise Manager Cloud Control

  The following procedure describes how to export objects using Oracle Enterprise Manager Cloud Control

  1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

     See Also:

     "Accessing the Net Services Administration Page"

  2. Select Directory Naming from the Administer list, and then select the Oracle home that contains the location of the directory server.

  3. Click Go.

     The Directory Naming page appears.

  4. Click the Net Service Names tab.

  5. In the Related Links section, click Import Net Service Names To Directory Server.

     The Import Net Service Names To Directory Server page appears.

  6. From the Oracle Context list in the Oracle Internet Directory Server Destination section, select Oracle Context to which you want to export the selected network service names.

  7. In the Net Service Names to Import section, select the network service names.

  8. Click Add to add the network service names to the directory.

     The network service name is added to the Directory Naming page.

• Export Objects using Oracle Net Manager

  The following procedure describes how to export objects using Oracle Net Manager:

  1. Start Oracle Net Manager.

     See Also:

     "Using Oracle Net Manager to Configure Oracle Net Services"

  2. If the tnsnames.ora file you want to export is not loaded in Oracle Net Manager, then select Open Network Configuration from the File menu to select the tnsnames.ora file to export to the directory.

  3. Select Directory from the Command menu, and then select Export Net Service Names.

     The Directory Server Migration wizard starts.

  4. Click Next.

     If network service names with multiple domain were detected in the tnsnames.ora file, then the Select Domain page appears. Continue to Step 5.

     If the network service names are not domain qualified, then the Select Net Service Names page appears. Skip to Step 6.

  5. Select the network domain whose network service names you want to export, and then click Next.

     The Select Net Service Names page appears.

  6. Select the network service names from the list to export, and then click Next.

     The Select Destination Context page appears.

  7. In the Select Destination Context page, do the following:

     1. From the Directory Naming Context list, select the directory entry that contains the Oracle Context. The directory naming context is part of a directory subtree that contains one or more Oracle Contexts.

     2. From the Oracle Context list, select the Oracle Context to which you want to export the selected network service names.

     3. Click Next.

     The Directory Server Update page appears with the status of the export operation.

  8. Click Finish to close the Directory Server Migration wizard.

After you create the directory naming entries, consider exporting the entries to a local tnsnames.ora file, and distributing that file to clients. Clients can use the locally saved file when a directory server is temporarily unavailable.

The following procedure describes how to export directory naming entries to a local tnsnames.ora file:

1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

   See Also:

   "Accessing the Net Services Administration Page"

2. Select Directory Naming from the Administer list, and then select the Oracle home that contains the location of the directory server.

3. Click Go.

   The Directory Naming page appears.

4. Click the Net Service Names tab.

5. In the Simple Search section, select Oracle Context and search criteria to see the network service names for a particular Oracle Context.

   The network service names display in the Results section.

6. In the Results section, click Save to tnsnames.ora.

   The Processing: Create tnsnames.ora File page appears, informing you of the creation process.

Configure the client LDAP naming adapter to use an Oracle wallet for authentication. This involves creating the wallet, mapping the DN in the certificate to the user's DN in the directory server, and configuring the sqlnet.ora file parameters.

1. Create an Oracle wallet with an LDAP server certificate in its truststore:
   1. Obtain an LDAP server certificate using the openssl s_client utility:

      openssl s_client -connect <OUD server host:SSL port> -showcerts </dev/null 2>/dev/null|openssl x509 -outform PEM >/tmp/ldapservercert.txt

      The -connect <OUD server host:SSL port> flag specifies the Oracle Unified Directory server host name and port to which you want to connect. The -showcerts flag displays the LDAP server certificate list sent by the server. The -outform flag extracts the certificate in a PEM format.

   2. Create an empty Oracle wallet using the orapki utility:

      orapki wallet create -wallet <wallet directory>

      The -wallet <wallet directory> flag specifies the location of the file system directory where you want to create the wallet.

   3. Add the LDAP server certificate to the wallet using the orapki utility:

      orapki wallet add -wallet <wallet directory> -trusted_cert -cert /tmp/ldapservercert.txt

      The -cert flag specifies the location of the file system directory for the LDAP server certificate.

   4. Add the LDAP user name to the wallet using the mkstore utility:

      mkstore -wrl <wallet directory> -createEntry oracle.ldap.client.dn <dn of username>

      <dn of username> specifies the distinguished name of the LDAP user who runs the database client application. For Microsoft Active Directory, you can also specify the userPrincipalName or down-level logon name (sAMAccountName) attribute.

      For example:

      mkstore -wrl /app/wallet -createEntry oracle.ldap.client.dn "cn=userinldap,dc=example,dc=com"

   5. Add the LDAP password to the wallet using the mkstore utility:

      mkstore -wrl <wallet directory> -createEntry oracle.ldap.client.password <password>

      <password> specifies the password of the LDAP user who runs the database client application.

      For example:

      mkstore -wrl /app/wallet -createEntry oracle.ldap.client.password "ldap_password"

   6. Enable auto login for the wallet using the orapki utility:

      orapki wallet -wallet <wallet directory> -auto_login

      For example:

      orapki wallet -wallet /app/wallet -auto_login

      Note:

      Auto login wallets are protected by file system permissions. Use operating system utilities to protect the wallet directory by granting read and write permissions only to the client.
2. Set the following parameters in the sqlnet.ora file:
   • NAMES.LDAP_AUTHENTICATE_BIND=TRUE
   • NAMES.LDAP_AUTHENTICATE_BIND_METHOD=LDAPS_SIMPLE_AUTH

   • WALLET_LOCATION=
       (SOURCE=
         (METHOD=<file>)
         (METHOD_DATA=
            (DIRECTORY=<wallet directory>)

     For example:

     WALLET_LOCATION=
       (SOURCE=
         (METHOD=FILE)
         (METHOD_DATA=
            (DIRECTORY=/app/wallet/)

   For more information on setting these parameters, see NAMES.LDAP_AUTHENTICATE_BIND, NAMES.LDAP_AUTHENTICATE_BIND_METHOD, and WALLET_LOCATION in Oracle Database Net Services Reference.

3. Using Oracle Net Manager, add one or more directory entries to the LDAP server.
4. Using the SQLPLUS utility or any database client, verify names resolution.

External naming refers to the method of resolving a network service name, stored in a third-party naming service, to a network address, such as network information services (NIS). Organizations and corporations using NIS as part of their systems infrastructure have the option to store network service names and addresses in NIS, using NIS external naming.

For example, when a user gives a command with a network service name (payroll) such as the following:

	SQLPLUS scott@payroll

NIS external naming on the node running the client program or database server acting as a client program contacts an NIS server located on the network, and passes the network service name to the NIS server. The NIS server resolves the network service name into an Oracle Net address and returns this address to the client program or server. The client program then uses this address to connect to Oracle Database.

An NIS server runs a program called ypserv, which handles name requests. The ypserv program stores different types of data in special files called maps. For example, passwords are stored in a map called passwd.byname. Oracle Database service names are stored in a map called tnsnames.

When a user uses a connect string, NIS external naming uses an RPC call to contact the ypserv program, and passes the Oracle network service name and the name of the map. The ypserv program looks in the tnsnames map for the name, such as payroll, and its address for the network service name. The address is returned to the client, and the client program uses the address to contact the database server.

$ adapters

Installed Oracle Net naming methods are:

Local Naming (tnsnames.ora)
Oracle Directory Naming
Oracle Host Naming
NIS Naming

Perform the following tasks:

• Task 1: Configure NIS Servers to Support NIS External Naming

  Before configuring servers to support NIS external naming, ensure that NIS is configured and running on the NIS servers that need to resolve Oracle Database network service names. Consult your NIS documentation for specifics. To complete this task, add the tnsnames map to the existing NIS maps, and then verify that the tnsnames map has been installed properly.

  1. Create a tnsnames.ora file, as specified in "Configuring the Local Naming Method".

     Note:

     Keep a copy of the tnsnames.ora file, preferably in the ORACLE_BASE_HOME/network/admin directory. You may need to use this file again later to load network service names into the NIS map.
  2. Convert the contents of the tnsnames.ora file to a tnsnames map using the tns2nis program using a command similar to the following:

     tns2nis tnsnames.ora
     

     The tns2nis program reads the tnsnames.ora file from the current directory. If the tnsnames.ora file is not located in the current directory, then use a full path name to specify its location, such as /etc/tnsnames.ora or ORACLE_BASE_HOME/network/admin/tnsnames.ora.

     The tnsnames map is then written into the current working directory.

     Note:

     The tns2nis program is supplied with NIS external naming.
  3. Copy the tnsnames map to the NIS server.
  4. Install the tnsnames map using makedbm, which is an NIS program.

     Note:

     This step must be performed by the person in charge of NIS administration.

     The makedbm program converts the tnsnames map into two files that the NIS server can read. The location of these files is operating system specific.

     For example, to generate and install a tnsnames map on Linux, as the root user, enter the following at the command line:

     # makedbm tnsnames /var/yp/'domainname'/tnsnames 

     See Also:

     Oracle operating system-specific documentation for details
  5. Verify tnsnames has been installed properly using the following command:

     ypmatch net_service_name tnsnames

     For example, you might enter the following command:

     ypmatch example.com tnsnames 
     

     This returns the length of the address in characters, followed by the address such as the following:

     99 (description=(address=(protocol=tcp) (host=sales)(port=1999)))
        (connect_data=(service_name=dirprod)))

• Task 2: Configure the Clients

  To configure clients, configure NIS as the first method specified in the NAMES.DIRECTORY_PATH parameter in the sqlnet.ora file. This parameter specifies the order of naming methods Oracle Net can use to resolve connect identifiers to connect descriptors.

  1. Start Oracle Net Manager.

     See Also:

     "Using Oracle Net Manager to Configure Oracle Net Services"
  2. In the navigator pane, select Profile from the Local menu.
  3. From the list in the right pane, select Naming.
  4. Click the Methods tab.
  5. From the Available Methods list, select NIS, and then click the right-arrow button.
  6. In the Selected Methods list, select NIS, and then use the Promote button to move the selection to the top of the list.
  7. Select Save Network Configuration from the File menu.

     The sqlnet.ora file updates with the NAMES.DIRECTORY_PATH parameter, listing nis first:

     NAMES.DIRECTORY_PATH=(nis, hostname, tnsnames)