6
Configuring Naming Methods and the Listener

This chapter describes how to configure your network.

Specific topics discussed are:

• Configuration Overview

• Setting Service Names and Instance Names

• Configuration Models

• Configuring Naming Methods and the Listener

• Configuring the Network with the Local Naming Method

• Configuring the Network with the Oracle Names Method

• Configuring the Network with the External Naming Method

• Configuring the Listener

• Configuring Protocol Addresses

Configuration Overview

Before a service, such as a database, can receive connections from clients, clients must be configured to use net service names. Net service names are network descriptions of service names. Each network description specifies one or more network routes to the service, including any number of Net8 components, such as listeners. Net service names also specify whether network connections should be load balanced among multiple listeners and/or fail over to an alternate listener if a network connection cannot be established.

Specifically, a net service name identifies the:

• network route to the service, including the location of the listener through a protocol address

• service name(s) used to identify the release 8.1 services, or Oracle System Identifier (SID) used to identify a pre-release 8.1 databases

• optional instance name of the release 8.1 service to which to connect

The listener address is used by the client to connect to the listener. Once connected, the client passes the address and service information to the listener.

When an instance starts, it registers the following registration information with the listener:

• service registration provides the listener with instance information, such as service names and instance names

• protocol address information with which the listener may connect to the instance

When listener receives a client's request for connect, it verifies the client information with the information it has received from the instance, as well as information it has stored in the LISTENER.ORA file. If the information matches, a connection is granted.

Client configuration is accomplished by creating a list of the net service names that map to services and addresses of listener destinations stored in a TNSNAMES.ORA client configuration file, an Oracle Names server, or another naming method. When an end user connects to a service, the service is identified by the net service name. For example:

sql> CONNECT username/password@net_service_name

Setting Service Names and Instance Names

A service name is a logical representation of a service, which may include a database. A service may comprise one or more instances. When creating a net service name, you must identify a release 8.1 service with a service name. Optionally, you may identify a release 8.1 instance with a instance name.

Shown below is a sample of TNSNAMES.ORA file, which shows how a net service provides a network description of a service:

net_service_name= 
(description= 
  (address= (protocol_address_information))
  (connect_data= 
     (service_name=service_name) 
     (instance_name=instance_name)))

In the example above, notice how the service name is identified by the SERVICE_NAME parameter and the instance name is identified by the INSTANCE_NAME parameter.

The service name is a string that is the global database name, a name comprised of the database name and domain name, entered during installation or database creation. If you are not sure what the global database name is, you can obtain it from the combined values of the SERVICE_NAMES parameter in the database initialization file, INITSID.ORA. For example, a service name may be SALES.COM, where SALES is the database name and COM is the domain.

The instance name includes the name of the instance. It is typically the SID entered during installation. If you are not sure what the SID is, you can obtain it from the INSTANCE_NAME parameter.

The table below describes the SERVICE_NAMES and INSTANCE_NAME parameters.

Parameter	Description
SERVICE_NAMES	One or more comma separated strings that represent the names of the services on the network. It is possible to provide multiple services names (by individual SERVICE_NAMES entries) so that different usages of a instance can be identified separately. Service names can also be used to identify a service that is available from multiple instances through the use of replication.
INSTANCE_NAME	A string value representing the name of instance and is used to uniquely identify a specific instance when multiple instances share common services names. INSTANCE_NAME should not be confused with the SID, which actually uniquely identifies the instances shared memory on a host.

Configuration Models

Net8 configuration is based upon one of three models:

Network Configuration Model	Suitable When...	Naming Method
Localized management	Network addresses are mapped in a TNSNAMES.ORA file on each node (no Oracle Names server).	Host Naming Local Naming External Naming
Centralized management	Networks where an Oracle Names server performs network address resolution. An Oracle Names server stores client configuration profiles in one location.	Oracle Names

Naming Methods

Net8 can resolve net service names using the following methods:

Naming Method	Description
Host Naming	Instead of net service names, clients use an alias that is mapped to a database's global database name during a connection. A host name is used to identify a database's global database name via an existing name resolution service. This name resolution service might be Domain Name Services (DNS), Network Information Service (NIS) or simply a centrally-maintained set of /etc/hosts files. Host naming allows users to connect to an Oracle server by simply providing the server computer's host name or host name alias. No client configuration is required to take advantage of this feature. This method is recommended for simple TCP/IP environments. Additional Information: See "Configuring the Network with the Host Naming Method".
Local Naming	Resolves net service names to network addresses by using information configured and stored on each individual client. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently. Additional Information: See "Configuring the Network with the Local Naming Method".
Oracle Names	Oracle Names stores names and addresses of all services on a network on an Oracle Names server. Connection requests are routed through an Oracle Names server, which resolves the net service name to a network address. The information is then returned to the client. Additional Information: See "Configuring the Network with the Oracle Names Method".
External Naming	External naming refers to net service name resolution by using a supported third-party naming service. Additional Information: See "Configuring the Network with the External Naming Method".

For further information regarding choosing the right method, see "Resolving Net Service Names".

Configuration Files

Depending on the naming method you use, the following configuration files may be created or modified in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms:

Configuration File	Description
LISTENER.ORA	Located on the server, this file includes addresses of all listeners on a server, and various control parameters used by the listener.
NAMES.ORA	Located on the Oracle Names server, this file includes he location, domain information, and optional configuration parameters for each Names server.
SQLNET.ORA	Includes the names resolution method. This file resides on clients.
TNSNAMES.ORA	Located on the clients, this file includes a list of net service names and their listener address and service descriptions.

See also the following:

• Appendix B, "Sample Configuration Files" for samples of these files

• Appendix C, "Configuration Parameters"for parameter information

Configuration of these files is described for each naming method in this chapter.

Configuring the Network with the Host Naming Method

Host naming can eliminate the need for service name lookup in the TNSNAMES.ORA configuration files in environments where simple connectivity is desired. However, host naming is not suitable for large or complex environments where advanced features such as connection pooling, external procedures, or heterogeneous services, which require additional connect information, are desired. In these cases, another naming method is recommended.

The host naming method is available for TCP/IP network environments only. When instances register with the listener, the global database name of the server, a name comprised of the database name and domain name, is registered. The global database name is mapped to host name and alias in an existing name resolution service. Client use the alias in their connect string to connect to the database.

Clients may connect to a server using the alias if:

• you are connecting to an Oracle8i database service with Net8 Server/Net8 Client software installed

• your client and server are connecting over a TCP/IP protocol

• all names are resolved through an IP address translation mechanism such as Domain Name Service (DNS), or a centrally maintained TCP/IP hosts file

• no advanced features like Oracle Connection Manager or security are requested or required

To configure the host naming method, perform these tasks:

Step 1: Configure the Listener with the Global Database Name

Step 2: Configure HOSTNAME as the First Naming Method

Step 3: Set Up Host Name Resolution Environment

Step 1: Configure the Listener with the Global Database Name

The global database name must be registered with the listener. How this registration takes place depends upon the release of the database.

Oracle8i release 8.1

If the database can find the listener, information about the database is automatically registered with the listener, including the global database name. The listener is found if:

• the default listener named LISTENER running on TCP/IP on port 1521 is running

• the LOCAL_LISTENER parameter is set in the INITSID.ORA file

If the database cannot find the listener, the LISTENER.ORA file must be configured with the GLOBAL_DBNAME parameter, as described in "Oracle8i Release 8.0 or Previous" below.

Oracle8i Release 8.0 or Previous

If the database is an Oracle8i release 8.0 database or Oracle7 database, database information is registered with the listener through the LISTENER.ORA file. For these database, statically configured the SID_LIST_listener_name section to include the GLOBAL_DBNAME parameter, as shown below:

sid_list_listener=(sid_list=
(sid_desc=
 (global_dbname=sales.com)
 (sid_name=db1)
 (oracle_home=/u01/app/oracle/8.0.5)

)

See "Configuring a Listener with Service Information" for further information.

Step 2: Configure HOSTNAME as the First Naming Method

Configure host naming as the first method specified in the NAMES_DIRECTORY_PATH parameter in the SQLNET.ORA file. This parameter specifies the order of naming methods Net8 will use to reconcile services.

To specify local naming as the first naming method:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose Naming from the drop-down list box.

4. Click the Methods tab.

5. Choose TNSNAMES from the Available Methods list, then click ">".
   1. Select TNSNAMES in the Selected Methods list, then use the Promote button to move the selection to the top of the list:

      
      

   2. Choose Save Network Configuration from the File menu.

   3. Choose Exit from the File menu to exit the Net8 Assistant application.

      The SQLNET.ORA file should contain an entry that lists HOSTNAME first in the NAMES.DIRECTORY_PATH parameter:

      names.directory_path=(hostname, tnsnames)
      

Step 3: Set Up Host Name Resolution Environment

The global database name must be resolved through an IP address translation mechanism, such as DNS, NIS, or a centrally-maintained TCP/IP host file, /etc/hosts. The alias created for the global database name must match the global database name.

It is important to note that the domain portion of the global database name must match the network domain.

For example, if a global database name of SALES.COM for a database exists on a machine named SALES-PC, the entry in the /etc/hosts file would like the following.

#IP address of server     host name   alias
144.25.219.146            sales-pc    sales.com

Clients would use SALES.COM in their connect string, as described in "Connecting to a Database". If the client and server are in the same domain of COM, the client only needs to enter SALES in the connect string.

Configuring the Network with the Local Naming Method

With the local naming method, net service names are added to the TNSNAMES.ORA file. A net service name is mapped to a network address contained in a connect descriptor. A connect descriptor contains the location of the listener through a protocol address and the service name of the service to which to connect. Clients use this net service name when making a connection with an application.

An example of a TNSNAMES.ORA file's basic syntax for a net service name mapped to a connect descriptor is shown in Figure 6-1. DESCRIPTION contains the connect descriptor, ADDRESS is the listener address, and CONNECT_DATA contains the service name.

Figure 6-1 Net Service Name Usage in TNSNAMES.ORA

net_service_name= 
(description= 
  (address= (protocol_address_information))
  (connect_data= 
     (service_name=service_name) 
  ) 
) 

Each connect descriptor can contain one or more listener addresses, as shown in Figure 6-2:

Figure 6-2 Multiple Listener Addresses

net_service_name= 
(description= 
  (address= (protocol_address_information))
  (address= (protocol_address_information))
  (address= (protocol_address_information))
  (connect_data= 
     (service_name=service_name) 
  ) 
) 






Note:



If there was only one list of addresses, it was required to use an ADDRESS_LIST.  

Optional parameters, such as connect-time failover, client load balancing, and Oracle Connection Manager features, may be set for a list of addresses within a connect descriptor or all addresses among multiple connect descriptors.

For more information about these features, see Chapter 7, "Enabling Optional Net8 Features" and "Local Naming Parameters (TNSNAMES.ORA)".

Configuration During Installation

After a Custom installation on the client or server, the Net8 Configuration Assistant prompts you to configure a naming methods. If the local naming method is chosen, the Net8 Configuration Assistants prompts you to configure net service names in the TNSNAMES.ORA file. If you choose to use the Net8 Configuration Assistant to create net service names, ensure the listener protocol addresses match in the TNSNAMES.ORA and LISTENER.ORA files. Use the online help for instruction.

Configuration After Installation

Net service names can be added to the TNSNAMES.ORA file at any time. To configure the local naming method, perform these tasks:

Step 1: Configure Net Service Names

Step 2: Configure TNSNAMES as the First Naming Method

Step 3: Distribute Configuration

Step 4: Configure the Listener

Step 1: Configure Net Service Names

To configure with the local naming method, use either the Net8 Assistant or the Net8 Configuration Assistant on the server:

Net8 Assistant

To use the Net8 Assistant:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Net Service Names folder in the directory tree. If net service names exist, they display in the tree structure.

3. Select Create from the Edit menu or click on the "+" button to create a new net service name. The Net Service Name Wizard starts.

4. Enter any name in the Net Service Name field, then click Next:

   
   

   If you want to be explicit, the net service name may be qualified with the client's domain. The net service name is automatically domain qualified if the NAMES.DEFAULT_DOMAIN parameter in SQLNET.ORA is specified. For further information, see "Configuring Domains".

5. Select the protocol the listener is configured to listen on (this protocol must also installed on the clients), then click Next:

   
   

6. Enter the appropriate listener protocol address information for your chosen protocol in the fields, then click Next:

   
   

   See "Configuring Protocol Addresses" for further information about protocol addresses.

   When configuring the listener to listen on TCP/IP for typical Net8 clients, you should choose the default port or 1521. If you do not, you must configure the LOCAL_LISTENER parameter in the INITSID.ORA file and resolve the listener name through a naming method. For further information about configuring non-default port numbers in LISTENER.ORA, see "Configuring a Listener that Uses a Non-Default Port".

7. If the destination service is release 8.1, click Oracle8i release 8.1, enter a service name in the Service Name field, then click Next:

   
   

   The service name is typically the global database name. See "Setting Service Names and Instance Names" for further information about the service name string to use.

   If destination service is prior to release 8.1, click Oracle8 Version 8.0 or Previous, enter a SID in the Database SID field, then click Next.

8. Click Test to verify the net service name will work, then click Next. Testing assumes the database and listener are running. If they are not, see "Net8 Component Startup Overview" to start components, or click Next to disregard testing and continue to step 10.

   A successful test results in "The connect test was successful." message in the Connect Test dialog box:

   
   

   If the test was not successful:

   • Ensure the database and listener are running, then click Test.

   • Click Change Login to change the user name and password for the connection, then click Test.

9. Click Close to dismiss the Connect Test dialog box.

10. Click Finish to save your configuration and dismiss Net Service Names Wizard.

11. Choose Save Network Configuration from the File menu.

12. Choose Exit from the File menu to exit the Net8 Assistant.

See also the following:

• "Configuring Advanced Connection Attributes for a Net Service Name" and "Configuring Multiple Address Options" to set optional address and multiple address characteristics.

• "Configuring Domains" to specify a domain to request net service names.

Net8 Configuration Assistant

To use the Net8 Configuration Assistant:

1. Start the Net8 Configuration Assistant:
   • On UNIX, run netca at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Configuration Assistant.

2. Select Local Net8 Service Name configuration, then click Next.

3. Click Create.

4. Follow the prompts in the wizard and online help to complete net service name creation.

   Note: If you select the Oracle8i release 8.1 database or service option, the service name you enter is typically the global database name. See "Setting Service Names and Instance Names" for further information about the service name string to use.

Step 2: Configure TNSNAMES as the First Naming Method

Configure local naming as the first method specified in the NAMES_DIRECTORY_PATH parameter in the SQLNET.ORA file. This parameter specifies the order of naming methods Net8 will use to reconcile services.

To specify local naming as the first naming method:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose Naming from the drop-down list box.

4. Click the Methods tab.

5. Choose TNSNAMES from the Available Methods list, then click ">".
   1. Select TNSNAMES in the Selected Methods list, then use the Promote button to move the selection to the top of the list:

      
      

   2. Choose Save Network Configuration from the File menu.

   3. Choose Exit from the File menu to exit the Net8 Assistant application.

      The SQLNET.ORA file should contain an entry that lists TNSNAMES first in the NAMES.DIRECTORY_PATH parameter:

      names.directory_path=(tnsnames, onames, hostname)
      

Step 3: Distribute Configuration

After one client is configured, it is best to simply copy over the TNSNAMES.ORA and SQLNET.ORA configuration files to the same location on the clients. This will ensure the files are consistent. Otherwise, you must use Net8 Assistant or Net8 Configuration Assistant on every client, introducing possible errors.

Step 4: Configure the Listener

Ensure the listener (located on the server) is configured to "listen on" on the same protocol and protocol address you configured for the net service name. By default, the listener should already be configured for your operating system's primary protocol, typically TCP/IP. For further information about configuring the listener, see "Configuring Protocol Addresses".

Configuring the Network with the Oracle Names Method

Oracle Names simplifies the setup and administration of global, client/server computing networks. Oracle Names makes network address and database link information available to all nodes throughout the network. Each database server's network address is identified with a simple service name. Client applications then can request a database connection with that name rather than a lengthy address. Oracle Names shields users and applications from changes made to the network infrastructure. It provides for centralized administration of network service names.

An Oracle Names server stores the following information:

Data	Description
database global database names and addresses	The Oracle Names server retrieves information about the database, including the global database name (database name and domain) and address, from the listener. The address is configured in the LISTENER.ORA file, and the global database name is registered during database startup or statically configured in the LISTENER.ORA file. You do not to register this information.
other Oracle Names server names and addresses	An Oracle Names server stores the names and addresses of all other Oracle Names servers in the same administrative region. If there is more than one administrative region in a network, the Oracle Names server will store the name and address of at least one Oracle Names server in the root administrative region and each of the immediate sub-regions. You do not need to register this information.
net service names	If you register net service name with the NAMESCTL control utility or the Net8 Assistant, an Oracle Names server stores them. An Oracle Names server also stores gateways to non-Oracle databases and Oracle RDB databases.
global database link	Database links allow a database to communicate with another database another. The name of a database link is the same as the global database name of the database to which the link points. Typically, only one database link should exist per database. The following types of database links may be created: You can create a private database link in a specific schema of a database. Only the owner of a private database link can use it. You can create a public database link for a database. All users and in the database can use it. You can create a global database link in Oracle Names server so anyone in the network can use it. Because the Oracle Names retrieves the global database name from the listener, a global database link that is the global database name is automatically registered with the Oracle Names server. Therefore, you do not need to register this information. User name and password credentials for the global database link may be registered with the Oracle Names server using the Net8 Assistatnt.These global database links may be supplemented with link qualifiers defined through the Net8 Assistant. Global database links may be superseded with private and public database links created by individual users. For more information about private and public database links, see Oracle8i Distributed Database Systems.
aliases	An Oracle Names server stores aliases or alternative service names for any defined net service name, database service or global database link. Aliases may be registered with the Oracle Names server using either the NAMESCTL control utility or Net8 Assistant.
Oracle Connection Managers	An Oracle Names server stores the names and listening addresses of all Oracle Connection Managers on the network. You do not to register this information.

Configuring Oracle Names involves the following tasks:

Step 1: Consider Oracle Names Options

Step 2: Install

Step 3: Create an Oracle Names Server

Step 4: Configure Clients and Database Servers To Use Oracle Names Servers

Step 5: Configure the Listener

Step 6: Register Data with the Oracle Names Server

Step 7: (Optional) Delegate Domains to Delegated Administrative Regions

Step 1: Consider Oracle Names Options

Prior to creating an Oracle Names server, you must decide whether:

• You need service registration data replicated continuously among Oracle Names servers, or want all Oracle Names servers within a region to store their registration data in an Oracle database.

• You need support for one or more administrative regions. An administrative region is a collection of Oracle Names servers in one or more domains, a grouping of network objects, such as databases. Networks with multiple administrative regions must have one root administrative region and one or more delegated administrative regions. Delegated administrative regions contain the domains and Oracle Names server addresses in any alternate regions which act as direct child regions of the root.

For more assistance with the decisions above, see "Oracle Names Architecture".

Step 2: Install

Ensure the following is installed:

• Oracle Names on its own machine that is designated as the Oracle Names server

• Net8 Client or SQL*Net Client on the clients

• Net8 Server or SQL*Net Server on the server

  
  

  Important: The Oracle Universal Installer does not install the $ORACLE_HOME/network/names directory on UNIX platforms. This directory is necessary for successful configuration. If it does not exist, manually create it.

Step 3: Create an Oracle Names Server

How an Oracle Names server is created depends upon whether you want region data:

• stored in tables, called a region database, in an Oracle database accessible to Oracle Names servers

  When information is added to an Oracle Names server, the information is stored in the database and in the Oracle Names server's cache files. If the database is unavailable, the information in the cache files is used.

• stored in an Oracle Names server's cache files and instantly replicated to the cache files of all other Oracle Names servers

The cache files are stored in $ORACLE_HOME/network/names on UNIX platforms and ORACLE_HOME\network\names on Windows NT:

File	Description
CKCFG.ORA	Contains information about the Oracle Names server configuration, similar to the NAMES.ORA file.
CKPCCH.ORA	Contains client cache information, such as the connect string information.
CKPREG.ORA	Contains information about data stored in the Oracle Names server, which is similar to a TNSNAMES.ORA file.

A default Oracle Names server named ONAMES_host is created during installation for a non-region database configuration. This Oracle Names is configured to listener on TCP/IP with port 1575. It contains basic configuration that does not include multiple domains or multiple regions. If you would like to use this Oracle Names server, skip this step and proceed to "Step 2: Discover Oracle Names Servers".

The following sections cover both modes:

• Store Data in a Region Database

• Store Data in Files

Whichever method you choose, Oracle Corporation recommends you create more than one Oracle Names server for the network, in case one should go down.

Store Data in a Region Database

To store service data in an Oracle database, perform the following tasks:

• Step 1: Configure the Database Server

• Step 2: Create Oracle Names Servers

• Step 3: Start the Oracle Names Server

Step 1: Configure the Database Server

To configure the database server:

1. Start the database if it is not currently running. Otherwise, go to step 2.
   1. Connect to the database as INTERNAL:

      sql> CONNECT internal/password
      

      where password is ORACLE for the INTERNAL user account by default.

   2. Start the database:

      sql> STARTUP;
      

2. Connect to the database as the SYSTEM user:

   sql> CONNECT system/password
   

   where password is MANAGER for the SYSTEM user account by default.

3. Create a user account and password:

   sql> CREATE user user
     identified by password
     default tablespace users
     temporary tablespace temp;
   
   

4. Run the NAMESINI.SQL script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin\names on Windows NT platforms. This script creates the tables needed by Oracle Names to store information. Optionally, run NAMESUPG.SQL to define old tables.

   sql> CONNECT user/password
   sql> @oracle_home/network/admin/namesini.sql;
   

Step 2: Create Oracle Names Servers

For each machine where Oracle Names is installed and where you want an Oracle Names server, create an Oracle Names server from the Net8 Assistant.

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. From the Net8 Assistant, click the Oracle Names Servers folder.

3. Choose Create from the Edit menu, or click on the "+" button to create a new Oracle Names server.

   The Names Wizard starts.

   The wizard guides you through the creation and configuration process, prompting for:

   • a unique Oracle Name Server name

   • a protocol address for the Oracle Names server

     If you choose TCP/IP, Oracle Corporation recommends using the default and officially registered port of 1575 for the Oracle Names server.

   • a choice to store information in a database or replicate information among Oracle Names servers

     (Click Use a region database.)

   • a protocol address for a database's listener

     If you choose TCP/IP, Oracle Corporation recommends using the default and officially registered port of 1521 for the listener.

   • database user ID, password, and service name or SID

   • whether or not this Oracle Names server is in the root administrative region

   If you specify this Oracle Names server is in the root administrative region, configuration completes.

   If you specify this Oracle Names server is not in the root administrative region, it assumed this Oracle Names server is in a delegated administrative region. The wizard then prompts you for the local administrative region's domain name and the address of an Oracle Names server in the root administrative region before completing.

   When the wizard completes, the following message appears:

   A Names Server, onames_server, has been created with default settings. Use the Configure Server section to modify the default configuration.

4. Select Save Network Configuration from the File menu.

5. Select Exit from the File menu to exit the Net8 Assistant application.

6. Repeat steps 2-5 to create additional Oracle Names servers in a region. The Net8 Assistant does not support creation of multiple Oracle Names servers on one machine.

The Net8 Assistant creates a NAMES.ORA file with at least the following settings:

• Oracle Names server name (NAMES.SERVER_NAME)

• Oracle Names server listening protocol address (NAMES.ADDRESSES)

• database information (NAMES.ADMIN_REGION)

A NAMES.ORA file is shown below with annotations of content:

#Oracle Names server name. The name should include the name of the domain 
this Oracle Names server is in.
names.server_name=namesvr2.com

#Oracle Names server listening protocol address
names.addresses=
  (address=(protocol=tcp)(host=namesrv2-pc)(port=1575)) 
  [(address=...))]

#Database repository information
names.admin_region=
  (region=
    (description=
      (address=(protocol=tcp)(host=sales-pc)(port-1521)) 
      (connect_data=
        (service_name=sales.com)
    )
    (userid=system)
    (password=password)
    (name=local_region)
    (refresh=86400)
    (retry=60)
    (expire=600)
    )
#If an Oracle Names server is in a delegated administrative region, identify 
the address of an Oracle Names server in the root administrative region.
names.domain_hints=
  (address=(protocol=tcp)(host=namesrv1-pc)(port=1575)) 

    

    # Specify the domain controlled by this region and the time to live (TTL). 
If this is the root administrative region, you must have NAME= (null) to 
identify the root domain properly.
names.domains=
  (domain=
    (name=)
    (min_ttl=86400)
  )
     


See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information.

Administering Multiple Domains

If you want the region to administer more than one domain, specify the additional domains in the NAMES.DOMAINS parameter with the Net8 Assistant:

1. Double-click on the Oracle Names server folder.

2. Select the Oracle Names server.

3. Select Domains from the drop-down list box.

4. Select the Domains tab.

5. Enter the domain name in the Domain Name field.

6. Enter the time-to-live information.

7. Click Add.

8. Select Save Network Configuration from the File menu.

9. Repeat steps 1-8 to create additional for additional domains.

In the example below, NAMES.DOMAINS contains a listing for the root, COM, ORACLE.COM, and HQ.ORACLE.COM domains. All the domain precedent to HQ.ORACLE.COM must be defined in order to define HQ.ORACLE.COM.

names.domains=
 (domain_list=
  (domain=
    (name=)
    (min_ttl=86400)
  )
  (domain=
    (name=com)
    (min_ttl=86400)
  )
  (domain=
    (name=oracle.com)
    (min_ttl=86400)
  )
  (domain=
    (name=hq.oracle.com)
    (min_ttl=86400)
  )
 )

Step 3: Start the Oracle Names Server

Start the Oracle Names server using either the Net8 Assistant or the NAMESCTL control utility:

Use the Net8 Assistant...

Use the control utility NAMESCTL...

Double-click on the Oracle Names server folder. Select the Oracle Names server. Select Manage Server from the drop-down list box. Select the Control tab. Click the Start radio button from the Server Operations field. Click Apply. The following message appears: Server started successfully. On Windows NT, a service called OracleHOME_NAMENamesONAMES_SERVER is created.

From the command line, enter: namesctl If the following error messages appear, ignore them. NNL-00024: warning: no preferred names servers in SQLNET.ORA NNL-00018: warning: could not contact default name server namesctl> start The START command of NAMESCTL loads the Oracle Names server into memory and tells it to begin executing. At startup, the Oracle Names server loads its configuration and data. On Windows NT, this creates a service called OracleORACLE_HOMENamesonames_serverService.

Store Data in Files

To store data in files and have it replicated between Oracle Names server during updates, performs these tasks:

• Step 1: Create an Oracle Names Server

• Step 2: Discover Oracle Names Servers

Step 1: Create an Oracle Names Server

For each machine where Oracle Names is installed and where you want an Oracle Names server, create an Oracle Names server from the Net8 Assistant:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. From the Net8 Assistant, click the Oracle Names Servers folder.

3. Choose Create from the Edit menu, or click on the "+" button to create a new Oracle Names server.

   The Names Wizard starts.

   The wizard guides you through the creation and configuration process, prompting you for

   • a unique Oracle Name Server name

   • a listening protocol address for the Oracle Names server

     If you choose TCP/IP, Oracle Corporation recommends using the default and officially registered port of 1575 for the Oracle Names server.

   • a choice to store information in a database or replicate information among Oracle Names servers

     (Click Don't use a region database.)

   • to identify if this is the first Oracle Names server in the region

     If this is not the first Oracle Names server in the region, the wizard then prompts you to discover the other Oracle Names servers or to specify the address of another Oracle Names server in the region.

   • to identify if this Oracle Names server is in the root administrative region

   If you specify this Oracle Names server is in the root administrative region, configuration completes.

   If you specify this Oracle Names server is not in the root administrative region, it assumed this Oracle Names server is in a delegated administrative region. The wizard then prompts you for the local administrative region's domain name and the address of an Oracle Names server in the root administrative region before completing.

   When the wizard completes, the following message appears:

   A Names Server, onames_server, has been created with default settings. Use the Configure Server section to modify the default configuration.

4. Select Save Network Configuration from the File menu.

5. Repeat Steps 2-4 to create additional Oracle Names servers in a region. The Net8 Assistant does not support creation of multiple Oracle Names servers on one machine.

The Net8 Assistant creates a NAMES.ORA file with at least the following settings:

• Oracle Names server name (NAMES.SERVER_NAME)

• Oracle Names listening protocol address (NAMES.ADDRESSES)

A NAMES.ORA file is shown below with annotations of content:

#Oracle Names server name. The name should include the name of the domain 
this Oracle Names server is in.
names.server_name=namesvr2.com

#Oracle Names server listening protocol address
  (address=(protocol=tcp)(host=namesrv2-pc)(port=1575)) 
  [(address=...))]


#If an Oracle Names server is in a delegated administrative region, identify 
the address of an Oracle Names server in the root administrative region.
names.domain_hints=
  (address=(protocol=tcp)(host=namesrv1-pc)(port=1575)) 


# Specify the domain controlled by this region and the time to live (TTL). 
If this is the root administrative region, you must have NAME= (null) to 
identify the root domain properly.
names.domains=
  (domain=
    (name=)
    (min_ttl=86400)
  )

See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information.

Administering Multiple Domains

If you want the region to administer more than one domain, specify the additional domains in the NAMES.DOMAINS parameter with the Net8 Assistant:

1. Double-click on the Oracle Names server folder.

2. Select the Oracle Names server.

3. Select Domains from the drop-down list box.

4. Select the Domains tab.

5. Enter the domain name in the Domain Name field.

6. Enter the time-to-live information.

7. Click Add.

8. Select Save Network Configuration from the File menu.

9. Repeat steps 1-8 to create additional for additional domains.

In the example below, NAMES.DOMAINS contains a listing for the root, COM, ORACLE.COM, and HQ.ORACLE.COM domains. All the domain precedent to HQ.ORACLE.COM must be defined in order to define HQ.ORACLE.COM.

names.domains=
 (domain_list=
  (domain=
    (name=)
    (min_ttl=86400)
  )
  (domain=
    (name=com)
    (min_ttl=86400)
  )
  (domain=
    (name=oracle.com)
    (min_ttl=86400)
  )
  (domain=
    (name=hq.oracle.com)
    (min_ttl=86400)
  )
 )

Step 2: Discover Oracle Names Servers

After all the Oracle Names servers are configured, have each Oracle Names, except the first Oracle Names server in the region, discover the other Oracle Names servers in a region.

See "Understanding Discovery" for a description of discovery.

On the machine where Oracle Names resides, use either the Net8 Assistant or the NAMESCTL control utility:

Use the Net8 Assistant...

Use the control utility NAMESCTL...

Double-click on the Oracle Names Server folder. Select an Oracle Names server. Choose Manage Server from the drop-down list box. Click the Control tab. Click the Start option button from the Server Operations field. Click Apply. The following message appears: Server started successfully. Choose Discover Oracle Names Servers from the Command menu. This produces an .SDNS.ORA file in $ORACLE_HOME/network/names on UNIX or SDNS.ORA in ORACLE_HOME\network\names on Windows platforms. This file contains the names and addresses of the Oracle Names server(s). This file is read to find the addresses of Oracle Names servers. The following message appears:"Discovered Oracle Names Server in the region. Please exit the tool and start again." If an Oracle Names server does not respond, and you know the network address of a particular Oracle Names server, a dialog will prompt you for that address.

Start the Oracle Names server: namesctl namesctl> start Discover the other Oracle Names servers: namesctl> reorder_ns This produces an .SDNS.ORA file in $ORACLE_HOME/network/names on UNIX or SDNS.ORA in ORACLE_HOME\network\names on Windows platforms. This file contains the names and addresses of the Oracle Names server(s). This file is read to find the addresses of Oracle Names servers. If an Oracle Names server cannot be found, and you know the network address of a particular Oracle Names server, enter the address at the prompt. For example: namesctl> reorder_ns (address=(protocol=tcp)(host=mail-pc)(port=1575)) Query another Oracle Names server to verify discovery. namesctl> query onames_server

Step 4: Configure Clients and Database Servers To Use Oracle Names Servers

To configure the client and database server machines:

1. Optionally, create a preferred Oracle Names server list, as described in "Configuring Preferred Oracle Names Servers".

2. Discover Oracle Names servers by creating an .SDNS.ORA file in $ORACLE_HOME\network\names on UNIX or SDNS.ORA file in ORACLE_HOME\network\names on Windows platforms. This file contains the order of names and addresses of the Oracle Names server(s) to contact. Client machines read this file to find the addresses of Oracle Names servers to contact. Use either the Net8 Assistant or the NAMESCTL utility.

   See "Understanding Discovery" for a description of discovery.

   Use the Net8 Assistant...

   Use the control utility NAMESCTL...

   Start the Net8 Assistant: -On UNIX, run netasst at $ORACLE_HOME/bin. -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant. Choose Discover Oracle Names Servers from the Command menu. This produces an .SDNS.ORA file in $ORACLE_HOME/network/names on UNIX or SDNS.ORA ORACLE_HOME\network\names on Windows platforms. This file contains the names and addresses of the Oracle Names server(s). This file is read to find the addresses of Oracle Names servers. The following message appears:"Discovered Oracle Names Server in the region. Please exit the tool and start again." If an Oracle Names server does not respond, and you know the network address of a particular Oracle Names server, a dialog will prompt you for the that address.

   Discover the other Oracle Names servers: namesctl namesctl> reorder_ns This produces an .SDNS.ORA file in $ORACLE_HOME/network/names on UNIX or SDNS.ORA in ORACLE_HOME\network\names on Windows platforms. This file contains the names and addresses of the Oracle Names server(s). This file is read to find the addresses of Oracle Names servers. If an Oracle Names server cannot be found, and you know the network address of a particular Oracle Names server, enter the address at the prompt. For example: namesctl> reorder_ns (address=(protocol=tcp)(host=mail-pc)(port =1575))

3. If you want Oracle Names to be the first method to reconcile net service names, set the NAMES_DIRECTORY_PATH parameter in the SQLNET.ORA file in the following manner:
   1. Click the Profile icon in the Net8 Assistant.

   2. Choose Naming from the drop-down list box.

   3. Click the Methods tab.

   4. Choose ONAMES from the Available Methods list, then click ">".

   5. Select ONAMES in the Selected Methods list, then use the Promote button to move the selection to the top of the list:

      
      

   6. Choose Save Network Configuration from the File menu.

   7. Choose Exit from the File menu to exit the Net8 Assistant application.

      The SQLNET.ORA file should contain an entry that lists ONAMES first in the NAMES.DIRECTORY_PATH parameter:

      names.directory_path=(onames, tnsnames, hostname)
      

4. Additional features that you may configure for how a client will use Oracle Names include:

   Net8 Assistant Option	SQLNET.ORA Parameter	Description
   Default Domain	NAMES.DEFAULT_DOMAIN	Indicates the domain name space from which the client will most often request an Oracle Names server. When set, this name will automatically be appended to any unqualified name in an Oracle Names request. Net8 sets the default domain to NULL by default.
   Maximum Wait Each Attempt	NAMES.INITIAL_RETRY_ TIMEOUT	Specifies how long a client will wait for a response from an Oracle Names server before reiterating the request to another Oracle Names server. Net8 will wait for 15 seconds by default.
   Attempts Per Names Server	NAMES.REQUEST_RETRIES	Specifies the number of times a client will attempt to iterate through the list of Oracle Names servers before allowing the operation to fail. Net8 will attempt to iterate through the list of Oracle Names servers once before allowing the operation to fail by default.
   Maximum Open Connections	NAMES.MAX_OPEN_ CONNECTIONS	Specifies how many connections an Oracle Names client may have open at one time. Net8 allows a client to have 10 connections open at any one time by default. This default value should be sufficient for almost all situations.
   Initial Preallocated Requests	NAMES.MESSAGE_POOL_ START_SIZE	Allows you to pre-allocate an initial number of messages in a client's message pool. These messages may be used for future requests to Oracle Names servers. Net8 allocates 10 messages in the pool by default. This default value should be sufficient for almost all situations.

   To add or configure these features:

   1. Click the Profile icon in the Net8 Assistant.

   2. Choose Naming from the drop-down list box.

   3. Click the Oracle Names tab.

   4. Enter data for the options indicated in the table on the previous page.

   5. Choose Save Network Configuration from the File menu.

   6. Choose Exit from the File menu to exit the Net8 Assistant application.

Step 5: Configure the Listener

Configure the listener with listening database protocol addresses if you are not using your operating system's primary protocol. For further information about configuring the listener, see "Configuring Protocol Addresses".

Additionally, set USE_PLUG_AND_PLAY_listener_name=ON in the LISTENER.ORA file with the Net8 Assistant. This permits the listener to register database information, such as the service name, SID, and global database name, with Oracle Names servers:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Listeners folder.

3. Click on a listener.

   =

4. Choose General Parameter from the drop-down list box.

5. Click Register Service with Oracle Names.

6. Select Save Network Configuration from the File menu.

7. Choose Exit from the File menu to exit the Net8 Assistant application.

Step 6: Register Data with the Oracle Names Server

As described in the table in "Configuring the Network with the Oracle Names Method", Oracle Names server store many kinds of information, including as database locations, Oracle Names server locations, net service names, aliases, global database links, and Oracle Connection Manager. Some of this information is automatically registered with the Oracle Names server because the database registers information with the listener. If you would like to store the following kinds of information, you must register it using either the Net8 Assistant or the NAMESCTL control utility:

• Net Service Names

• Global Database Links Credentials and Database Qualifiers

• Aliases

Registration only needs to occur with one Oracle Names server in an administrative region. The other Oracle Names servers will see the information if data is stored in a region database, or the information will be propagated to other Oracle Names if you chose not to use a region database.

After registering these kinds of information, you should query them, as described in "Testing Network Objects Using NAMESCTL or the Net8 Assistant".

Net Service Names

Oracle Corporation advises creating a net service name for each service. If a net service name is not created, a user trying to connect will have to pass the global database name to make a connection. Rather than provide this information to your end users, create a net service name for the service.

Use either the Net8 Assistant or the NAMESCTL control utility:

Use the Net8 Assistant...

Use the control utility NAMESCTL...

Start the Net8 Assistant: -On UNIX, run netasst at $ORACLE_HOME/bin. -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant. Double-click on the Oracle Names server folder. Select an Oracle Names server. Choose Manage Data from the drop-down list box. Click the Net Service Names tab. Select Add. Enter an easy-to-remember alias in the Service Name field. Choose a protocol and enter the listener address. Additional Information: See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information. Enter the service name for the database, and choose the session type. Click Execute. Select Save Network Configuration from the File menu. Select Exit from the File menu to exit the Net8 Assistant application.

Create and register a net service name with the Oracle Names server: namesctl namesctl> register net_service_name -D address_data For example, to register a net service name of SALES with a default TCP/IP listening address, enter: register sales -D (description=(address=(protocol-tcp)(host=sales-pc)( port=1521))) Additional Information: See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information.

If you have been using local naming as your configuration method and want to migrate to an Oracle Names configuration, the net service name information used in the TNSNAMES.ORA file can uploaded to an Oracle Names server. To load information from a local naming configuration file into an Oracle Names server, use either the Net8 Assistant or the NAMESCTL control utility:

Use the Net8 Assistant...	Use the control utility NAMESCTL...
Select an Oracle Names server. Select Manage Data from the drop-down list box. Select Load. Enter the path for your current master local naming configuration file in the File field. Click Execute. Select Save Network Configuration from the File menu. Select Exit from the File menu to exit the Net8 Assistant application.	From the command line, enter: namesctl namesctl> load_tnsnames file_name

Global Database Links Credentials and Database Qualifiers

Oracle Corporation recommends creating one global database link per database. A global database link that is the global database name is automatically registered with the Oracle Names server, such as SALES.COM.

For example, a connection to a remote database with the global database link would be:

sql> CONNECT @sales.com

Therefore, you do not need to register this information unless you want to enter user name and password credentials for it.

To register a global database link, use either the Net8 Assistant or the NAMESCTL control utility. Because the NAMESCTL utility is limited in global database link registration, Oracle Corporation recommends you use the Net8 Assistant.

Use the Net8 Assistant...

Use the control utility NAMESCTL...

Start the Net8 Assistant: -On UNIX, run netasst at $ORACLE_HOME/bin. -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant. Double-click on the Oracle Names server folder. Select an Oracle Names server. Choose Manage Data from the drop-down list box. Click the DB Links tab. Select Add. Enter the global database link in the DB Link Name field. NOTE: If the GLOBAL_NAMES parameter has been set to TRUE in the INITSID.ORA file, the name entered must be the global database name. Enter valid user name and password credentials for the database in the User and Password fields. Click Execute. If you want to use a link qualifier, see "Adding Link Qualifiers". Select Save Network Configuration from the File menu. Select Exit from the File menu to exit the Net8 Assistant application.

Create and register a global database link with the Oracle Names server: namesctl namesctl> register dblink-d address_data For example, to register a global database link of SALES.COM with a default TCP/IP listening address, enter: register sales.com -d (description=(address=(protocol-tcp)(host=sale s-pc)(port=1521))) Additional Information: See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information. The NAMESCTL utility will not permit user name and password credentials.

While one global database link per database is recommend, there is no limit on the number of link qualifiers that may be added. Link qualifiers are appended to global database link to provide alternate settings for the database user name and password credentials. For example, a link qualifier of RDBMS.OMD can be appended to SALES.COM. A connection to a remote database with the global database link and link qualifier would be:

sql> CONNECT @sales.com@emp

Adding Link Qualifiers

Link qualifiers are primarily for older Oracle database environments where multiple database links are used. Rather than use multiple database links, multiple link qualifiers can be created for a database link.

To register a global link qualifier for a global database link, use the Net8 Assistant. The NAMESCTL utility does not support creation of link qualifiers.

1. Follows steps 1-8 on the procedure on the previous page.

2. Click DB Qualifiers.

3. Click Create Qualifier.

   The Database Qualifier dialog box appears:

   

4. Enter a name for the link qualifier, and valid user name and password credentials, then click OK.

   The link qualifier is added to the DB Qualifiers list box:

   
   
5. Repeat steps 3-5 for each link qualifier you want to add.

6. Click Execute.

7. Select Save Network Configuration from the File menu.

8. Select Exit from the File menu to exit the Net8 Assistant application.

To verify a global database link and link qualifier is working correctly:

1. Connect to the remote database:

   sql> CONNECT user_name/password@db_link;
   sql> CONNECT user_name/password@db_link@link_qualifier;
   
   

   For example:

   sql> CONNECT scott/tiger@sales.com;
   sql> CONNECT scott/tiger@sales.com@emp;
   
   

2. Perform a SELECT statement on a table the user is authorized for:

   sql> SELECT * from  table@db_link;
   sql> SELECT * from  table@db_link@link_qualifier;
   
   

   For example:

   sql> SELECT * from EMP@sales.com;
   sql> SELECT * from EMP@sales.com@emp;
   
   

For more information about database links, see Oracle8i Distributed Database Systems.

Aliases

An alias can be used for type of item stored in the Oracle Names server, such as a Oracle Names server, net service name, or global database link.

To register a global database link, use either the Net8 Assistant or the NAMESCTL control utility.

Use the Net8 Assistant...

Use the control utility NAMESCTL...

Start the Net8 Assistant: -On UNIX, run netasst at $ORACLE_HOME/bin. -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant. Double-click on the Oracle Names server folder. Select an Oracle Names server in the administrative region. Choose Manage Data from the drop-down list box. Click the Aliases tab. Select Add. Specify the sub-domain in the Domain Name field. Enter the Oracle Names server name in the Name Server Name field and Click Execute. Select Save Network Configuration from the File menu. Select Exit from the File menu to exit the Net8 Assistant application.

Create and register an alias with the Oracle Names server: namesctl namesctl> register alias/i> -d address_data For example, to register a net service name of SALES with a default TCP/IP listening address, enter: register sales -d (description=(address=(protocol-tcp)(host=sale s-pc)(port=1521))) Additional Information: See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information.

Step 7: (Optional) Delegate Domains to Delegated Administrative Regions

If delegated administrative regions are configured, the upper-level administrative region must delegate sub-domains to the delegated administrative regions. Otherwise, the Oracle Names servers in the upper-level administrative region will assume authority over all sub-domains.

Once a domain is delegated, the Oracle Names servers in the current region will forward subsequent operations to the sub-region where the domain is administered by Oracle Names servers.

To delegate a domain, use either the Net8 Assistant or the NAMESCTL control utility.

Use the Net8 Assistant...

Use the control utility NAMESCTL...

Start the Net8 Assistant: -On UNIX, run netasst at $ORACLE_HOME/bin. -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant. Double-click on the Oracle Names server folder. Select an Oracle Names server in the upper-level region. Choose Manage Data from the drop-down list box. Click the Topology tab. Select Delegate Domain. Enter the name of the sub-domain in the Domain Name field. Enter the Oracle Names server that serves the domain in the Names Server Name field, and the listening address for the Oracle Names server. Additional Information: See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information. Click Execute. Select Save Network Configuration from the File menu. Select Exit from the File menu to exit the Net8 Assistant application.

Create and register an alias with the Oracle Names server: namesctl namesctl> delegate_domain domain_name onames_server [(description=(address_list=] (address= ...)[))] Additional Information: See "Configuring Protocol Addresses" for more information about protocol syntax needed for address information. For example, to delegate domain ACME.COM serviced by NAMESRV3.ACME.COM, enter: delegate_domain acme.com namesrv3.acme.com (address=(protocol-tcp)(host=namesrv3-pc)(port =1575)))

Configuring the Network with the External Naming Method

External naming refers to the method of resolving a net service name to a network address by using a supported non-Oracle naming service. External naming resolve net service names stored in customers' native (non-Oracle) naming services. They include:

• Network Information Service (NIS)

• NetWare Directory Service (NDS)

Configure NIS

Organizations and corporations already using Network Information Service (NIS) as part of their systems infrastructure have the option to store Oracle net service names and addresses in NIS, using NIS External Naming.

When a user gives a command such as

	sqlplus scott/tiger@payroll

(where "payroll" is an Oracle net service name) NIS External Naming on the node running the client program (or server acting as a client program) contacts an NIS server located somewhere in the network, and passes the net service name to the NIS server. The NIS server resolves the net service name into a Net8 address and returns this address to the client program (or server acting as a client program). The client program then uses this address to connect to the Oracle database.

A machine that acts as an NIS server runs a program called ypserv, which handles name requests. ypserv stores different types of data in special files called maps. For example, passwords are stored in a map called passwd.byname. Oracle database net service names are stored in a map called tnsnames.

When a user issues a command like the one in the previous section, NIS External Naming uses an RPC call to contact the ypserv program and passes the Oracle net service name "payroll" and the name of the map--tnsnames. The ypserv program looks in the tnsnames map for the name "payroll" and its corresponding value, which is the address for the net service name. The address is returned to the client, and the client program (or server acting as a client program) uses this address to contact the database server.

System Requirements

NIS External Naming requires SQL*Net 2.2 or greater.

Step 1: Configure NIS Servers to Support the NIS External Naming

Before configuring servers to support the NIS External Naming, make sure that NIS is configured and running on the NIS servers that need to resolve Oracle database net service names. Consult your NIS documentation for specifics.

Add the "tnsnames" Map to the Existing Set of NIS Maps

To add the tnsnames map to the existing set of NIS maps:

1. Create a TNSNAMES.ORA file, as specified in "Configuring the Network with the Local Naming Method".

   Note: Keep a copy of the TNSNAMES.ORA file, preferably in $ORACLE_HOME/network/admin directory. You may need to use this file again later to load net service names into the NIS map.

2. Convert the contents of the TNSNAMES.ORA file to a tnsnames map using the tns2nis program.

   Note: The tns2nis program is supplied with NIS External Naming on the Oracle Universal Installer tape or disk.

   For example, run tns2nis on the command line with one argument:

   		tns2nis tnsnames.ora
   
   

   tns2nis reads the NATIVE.ORA file from the current directory. (If TNSNAMES.ORA is not located in the current directory, you can use a full path name to specify its location--for example, /etc/native.ora or $ORACLE_HOME/network/admin/tnsnames.ora).

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

3. Copy tnsnames to the NIS server, if it is not already there.

4. Install the tnsnames map using makedbm, which is an NIS program. Refer to your NIS documentation for more information.

   Note: This step should be performed by the person in charge of NIS administration.

   makedbm converts the tnsnames map into two files that the NIS server can read. The location of these files is platform-specific. Refer to your platform-specific documentation for details.

   For example, to generate and install a tnsnames map on the Sun Solaris, as root enter the following at the command line

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

Verifying that the "tnsnames" Map Has Been Properly Installed

You can test the NIS server to see if the map has been installed properly by typing a command with the format:

ypmatch net_service_name tnsnames 

For example, you might enter:

ypmatch payroll.com tnsnames 

This returns the length of the address (in characters) followed by the address; for example:

	99 (description=(address=(protocol=tcp)

  (host=garlic)(port=1999)))

  (connect_data=(service_name=dirprod)))

Step 2: Configure Clients

To configure clients, configure NDS as the first method specified in the NAMES_DIRECTORY_PATH parameter in the SQLNET.ORA file. This parameter specifies the order of naming methods Net8 will use to reconcile services.

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose Naming from the drop-down list box.

4. Click the Methods tab.

5. Choose NIS from the Available Methods list, then click ">".

6. Select NIS in the Selected Methods list, then use the Promote button to move the selection to the top of the list:

   
   

7. Choose Save Network Configuration from the File menu.

8. Choose Exit from the File menu to exit the Net8 Assistant application.

   The SQLNET.ORA should contain an entry that looks like the following:

   names.directory_path=(nis, tnsnames, hostname)
   

Configure NDS

NDS External Naming allows you to use native NDS naming conventions to connect to an Oracle database on a Novell NDS-enabled network. After the NDS External Naming has been installed on clients and servers, users can enter:

username/password@net_service_name

NDS External Naming provides network users with the following benefits:

• Allows clients to use simple NDS names (partial or full) when connecting to a database.

• Simplifies the maintenance of the TNS addresses; one change will affect all clients using NDS External Naming.

• Reduces network traffic by eliminating the need for the listener to advertise.

Client Operations

The NDS External Naming resides on the client workstation and translates the NDS object name into a TNS address. The client code gets attributes from the NDS tree for the NDS object whose name matches the Oracle net service name. This name can be a full name or a partial name. If it is a partial name, it will be qualified with respect to the current name context.

NetWare Server Operations

There are three aspects to the server-side NDS External Naming:

• Schema Extension

• SAP (Service Address Protocol) Disabling

• Net Service Name and Address Storage in NDS

Schema Extension

During the Oracle installation process on a NetWare 4 server the NDS schema is extended to include an object class called "ORACLE:DBInstance". For NDS External Naming to function, this class will need an attribute called "ORACLE:TNSAddress". If the class does not exist, it is created and will include the TNSAddress attribute. If the class exists but the TNSAddress attribute does not, the class will be modified. The NLM that performs this during installation is called ORASCHEM.NLM.

SAP (Service Address Protocol) Disabling

The SPX protocol for NetWare looks for a value in CONFIG.ORA called ORACLE_SAP. The value of this parameter is ON or OFF. If this parameter is not specified, the default is ON. This has performance implications for SPX networks. When ORACLE_SAP is ON, the SQL*Net listener advertises its address using SAP (Service Advertising Protocol). When ORACLE_SAP is set to OFF, the SQL*Net listener relies on NDS to deliver information to its clients.

If your network consists entirely of NDS enabled clients (that is, clients using NetWare 4 and above), you will get better network performance if you edit the CONFIG.ORA file to set ORACLE_SAP to OFF.

Net Service Name and Address Storage in NDS

When the listener is started, it stores its address in the NDS database by locating the Oracle database instance that resides on its server.

At that point, the address(es) is (are) accessible to the client from the NDS database

System Requirements

NDS External Naming requires SQL*Net 2.2 or later and Oracle 7.2 or later. It can be used with any client running Novell libraries, but requires NetWare 4.1 or later on the server.

Configure Clients

To configure clients:

1. Configure NDS as the first method specified in the NAMES_DIRECTORY_PATH parameter in the SQLNET.ORA file. This parameter specifies the order of naming methods Net8 will use to reconcile services.
   1. Start the Net8 Assistant:

      -On UNIX, run netasst at $ORACLE_HOME/bin.

      -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

   2. Click the Profile icon.

   3. Choose Naming from the drop-down list box.

   4. Click the Methods tab.

   5. Choose NDS from the Available Methods list, then click ">".

   6. Select Novell in the Selected Methods list, then use the Promote button to move the selection to the top of the list:

      
      

   7. Choose Save Network Configuration from the File menu.

   8. Choose Exit from the File menu to exit the Net8 Assistant application.

      The SQLNET.ORA file should contain an entry that lists NOVELL first in the NAMES.DIRECTORY_PATH parameter:

      names.directory_path=(novell, tnsnames, hostname)
      

2. Optionally, configure a typeless or typed name.
   • To specify a typeless name:

     Add the following parameter to the SQLNET.ORA file to specify the default name context in which to look for the name to be resolved.

     	native_names.nds.name_context
     

     Note: You must add this parameter manually to the SQLNET.ORA file. It cannot be created using Net8 Assistant.

     For example, if the name of the database object is "Payroll.Finance.Oracle" and the SQLNET.ORA parameter is NATIVE_NAMES.NDS.NAME_CONTEXT=Finance.Oracle, then the name "Payroll" will be qualified to ".Payroll.Finance.Oracle". This is an example of a typeless name.

     Note: The leading dot designates this as a full NDS name. If you want to override the name context parameter in SQLNET.ORA, then you can specify the full NDS name in the connect string by using a leading dot.

   • To specify a typed name, enter a parameter and value in SQLNET.ORA like the following:

     native_names.nds.name_context=OU=Finance.O=Oracle
         
     
              

     This line will be parsed to produce the typed name

     CN=Payroll.OU=Finance.O=Oracle.
         
     
              

     This parameter works similarly to the NET.CFG parameter "name context". The name context in SQLNET.ORA will override the entry in NET.CFG. If the SQLNET.ORA parameter is not specified, the NET.CFG parameter will be used. If no name context is specified in either file, it defaults to [root]. See the Novell client documentation for more information about the NET.CFG parameters.

     Note: The default name context specified in SQLNET.ORA cannot contain a leading dot. This will result in an NDS error code of -309 (ERR_EXPECTED_IDENTIFIER): The parameter being parsed is not typed.

Configure the Server

To configure the NetWare Server:

1. Configure NDS as the first method specified in the NAMES_DIRECTORY_PATH parameter in the SQLNET.ORA file. This parameter specifies the order of naming methods Net8 will use to reconcile services.
   1. Start the Net8 Assistant:

      -On UNIX, run netasst at $ORACLE_HOME/bin.

      -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

   2. Click the Profile icon.

   3. Choose Naming from the drop-down list box.

   4. Click the Methods tab.

   5. Choose Novell from the Available Methods list, then click ">".

   6. Select Novell in the Selected Methods list, then use the Promote button to move the selection to the top of the list.

   7. Choose Save Network Configuration from the File menu.

   8. Choose Exit from the File menu to exit the Net8 Assistant application.

2. Optionally, add the following parameter to the CONFIG.ORA file located in $ORACLE_HOME/nlm:

   	oracle_sap=[off|on]
   

ORACLE_SAP can be set to either ON or OFF. When ORACLE_SAP is ON, the listener advertises its address using SAP (Service Advertising Protocol). When ORACLE_SAP is set to OFF, the listener relies on NDS to deliver information to its clients. If not specified in CONFIG.ORA, ORACLE_SAP defaults to on. To reduce network traffic on a network where all clients use NDS, use:

	oracle_sap=off

Known Limitations

Following are some known limitations when using the NDS External Naming:

• The TNS address stored in the NDS database cannot be more than 2048 characters in length.

• You cannot use more than one listener per database instance. If you do, the last listener to start will overwrite any other TNS address stored in the database object.

• If SID support is enabled on the server, you should not use a NULL SID for any of the database instances. If a NULL SID is used for one of the instances, you cannot connect to it using SQL*Net version 2 or Net8.

• If SID support is not enabled, the last SID specified in the listener's SID_LIST will be the one used. In this case, the SID is transparent to the user and database. The user does not see it and the database ignores it.

  Note: SID support is controlled by the following parameter in the CONFIG.ORA file: nw_enable_sid_support=[true|false]

Configuring the Listener

Services coordinate their session with the help of a listener. The listener receives connection requests on behalf of a client application. Listener are configured to "listen on" an address specified in a listener configuration file, LISTENER.ORA, for a database service or non-database service. Once the LISTENER.ORA file is configured, the listener may be managed with the Listener Control Utility (LSNRCTL).

An Oracle8i database instance registers itself with the listener. Prior releases required configuration of the database SID description information. In order to take advantage of release 8.1 features, use the latest listener.

By default the following listening endpoints are configuration automatically during installation:

• IPC for connections to external procedures

• TCP/IP for a Net8 client connection to the Oracle database

• TCP/IP for a IIOP client connection to the Java option

Additionally, the SID_LIST is automatically configured for the database and external procedures.

The default LISTENER.ORA is shown below with annotations of content:

listener=
  (description_list=
    # ipc listenening endpoint for external procedures' connections
    (description=
      (address_list=
        (address=(protocol=ipc)(key=extproc0))
      )
    )
    # tcp/ip listenening endpoint for java option connections
    (description=
      (protocol_stack=
        (presentation=giop)
        (session=raw)
      )
      (address_list=
        (address=(protocol=tcp)(host=sales-pc)(port=2481))
      )
    )
    # tcp/ip listenening endpoint for database connections
    (description=
      (address_list=
        (address=(protocol=tcp)(host=sales-pc)(port=1521))
      )
    )
  )
# list of services for a listener named LISTENER to receive requests for
sid_list_listener=
  (sid_list=
    # service description for external procedures
    (sid_desc=
      (sid_name=plsextproc)
      (oracle_home=c:\orahome81)
      (program=extproc)
    )
    # service description for the database specified
    (sid_desc=
      (global_dbname=sales.com)
      (oracle_home=c:\orahome81)
      (sid_name=sales)
    )
  )

The following listener configuration items are addressed in this section:

• Re-Starting the Listener After a LISTENER.ORA File Modification

• Configuring Listener Protocol Addresses

• Using a Listener Name Other than LISTENER

• Handling Larger Volumes of Connection Requests

• Configuring a Listener with Service Information

See also the following:

• "Configuring Net8 for External Procedures" for further information about external procedure configuration

• "Configuring Java Option Connections" for further information about Java option and IIOP client configuration

Re-Starting the Listener After a LISTENER.ORA File Modification

If you modify the LISTENER.ORA, the listener must be stopped and re-started with the LSNRCTL utility.

To stop the listener:

lsnrctl
lsnrctl> start [listener_name]

To stop the listener:

lsnrctl
lsnrctl> stop [listener_name]

listener_name is the name of the listener defined in the LISTENER.ORA file. It is not necessary to identify the listener if you are using the default listener, named LISTENER.

For further information, see:

• "Net8 Component Startup Overview"

• "Listener Control Utility (LSNRCTL)"

Configuring Listener Protocol Addresses

The listener address you configured for either local naming or Oracle Names must also be configured in LISTENER.ORA. During a Typical or Minimal installation, TCP/IP is automatically configured in the LISTENER.ORA. The other protocols, however, are not configured. To configure other protocol listener addresses:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Listeners folder.

3. Click on a listener.

   Note: If a LISTENER.ORA has been configured during installation and listener has never been started with the LSNRCTL control utility, the Listeners folder will not display a listener. If this occurs, exit the Net8 Assistant, start the listener (as described in "Net8 Component Startup Overview"), and start the Net8 Assistant again.

   If a listener does not exist because a LISTENER.ORA was not installed:

   1. Select Create from the Edit menu or click on the "+" button to create a new LISTENER.ORA file.

   2. Enter a unique listener name in the Choose Listener Name dialog box.

4. Choose Listening Locations from the drop-down list box.

5. Click Add Address.

6. Choose the protocol and enter the requested protocol address information, as described on "Configuring Protocol Addresses":

   
   

7. Choose Net8 Client for typical client connections to database services, or choose IIOP Clients for client connection to the Java option.

   When configuring the listener to listen on TCP/IP for typical Net8 clients, you should choose the default port or 1521. If you do not, you must configure the LOCAL_LISTENER parameter in the INITSID.ORA file and resolve the listener name through a naming method. For further information about configuring non-default port numbers in LISTENER.ORA for Net8 clients, see "Configuring a Listener that Uses a Non-Default Port".

   If IIOP Clients was chosen, ensure the protocol was TCP/IP on port 2481 or TCP/IP with SSL on port 2482. If you do not, you must configure the LOCAL_LISTENER parameter or the MTS_DISPATCHERS parameter's LISTENER attribute in the INITSID.ORA file, and resolve the listener name through a naming method. For further information about configuring non-default port numbers in LISTENER.ORA for IIOP clients, follow the steps in "Configuring a Non-Default Listener".

8. Repeat Step 5-7 for additional protocols.

9. Select Save Network Configuration from the File menu.

10. Choose Exit from the File menu to exit the Net8 Assistant application.

For example, a LISTENER.ORA file statically configured with the for SPX address for service named oraservc1 in addition to the default TCP/IP address is shown below:

listener=
  (address= 
     (protocol= tcp)
     (host= sales-pc) 
     (port= 1521)
   )
  (address= 
     (protocol= spx)
     (service=orasrvc1) 
   )

Configuring a Listener that Uses a Non-Default Port

If you configure a TCP/IP listener addresses that does not use the default 1521 port for Net8 clients, you must configure the LOCAL_LISTENER parameter in the INITSID.ORA file and resolve it with a net service name entry in the TNSNAMES.ORA file or Oracle Names server.

Configuring the LOCAL_LISTENER Parameter

The LOCAL_LISTENER parameter should be configured as follows:

local_listener=listener_name

In order for the dispatcher to register its information with a non-default listener, the listener name you specified for the LOCAL_LISTENER parameter must be resolved through a naming method, such as a TNSNAMES.ORA file on the server or an Oracle Names server.

The entry should only contain the address of the listener, not the service name information in the CONNECT_DATA portion.

Configuring a TNSNAMES.ORA File

The Net8 Assistant does not allow you to configure a TNSNAMES.ORA without the CONNECT_DATA information. Therefore, Oracle Corporation recommends you create the TNSNAMES.ORA manually.

If the listener name is LISTENER1, the listening endpoint uses TCP/IP on port 1421, and the chosen naming method is the local naming method, the entry in the TNSNAMES.ORA would be:

listener1.us.oracle.com= 
(description= 
  (address= 
     (protocol= tcp)
     (host= sales-pc) 
     (port= 1421)
  )
)

Multiple addresses are supported, but multiple address connect-time failover and client load balancing features are not supported. Oracle Connection Manager's SOURCE_ROUTE parameter is supported.

Configuring an Oracle Names Server

An entry for the listener can be made through an Oracle Names server through the Net8 Assistant:

1. Start Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Select the Oracle Names Servers folder.

3. Click on an Oracle Names server.

4. Select Manage Data from the drop-down list box.

5. Select the Advanced tab:

6. Click Add, and enter the listener name in the Name field, A.SMD record type in the Type field, and enter the address in the Value field, such as:

   (address=(protocol= tcp)(host= sales-pc)(port= 2481))
   
   

7. Choose Save Network Configuration from the File menu.

8. Choose Exit from the File menu to exit the Net8 Assistant.

Using a Listener Name Other than LISTENER

By default the listener name is LISTENER. The listener name must be unique on any given node. The listener can be given any name.

To provide a listener with a new name:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Listeners folder.

3. Click on a listener.

4. Choose General Parameters from the drop-down list box:

   
   

5. Modify the Listener Name field with the new listener name.

6. Select Save Network Configuration from the File menu.

7. Choose Exit from the File menu to exit the Net8 Assistant application.

Handling Larger Volumes of Connection Requests

If you expect the listener to handle large volumes of connection requests, you may specify a queue for the process. This will allow the listener to dynamically handle larger numbers of concurrent connection requests.

To specify a queue size for a listener, enter a value to the QUEUESIZE parameter at the end of any listening address:

listener=
  (address= 
     (protocol= tcp) 
     (host= sales-pc) 
     (port= 1521)
     (queuesize=20)
   )

Configuring a Listener with Service Information

In order for the listener to accept client requests to an Oracle8i release 8.0 or Oracle7 database, the LISTENER.ORA file must be configured with information about the database. Static configuration is also required for other services, such as external procedures and heterogeneous services, and some management tools, including Oracle Enterprise Manager.

See Chapter 7, "Enabling Optional Net8 Features" for more information about statically configuring the listener for external procedures and heterogeneous services. See the Oracle Enterprise Manager Configuration Guide for Oracle Enterprise Manager configuration.

To configure information about database instances that the listener is servicing, you will need to provide the following information in the listener configuration file:

Net8 Assistant Option	LISTENER.ORA Parameter	Description
System Identifier (SID)	SID_NAME	The system identifier or SID is the Oracle system ID for the database server, as provided by the INSTANCE_NAME parameter in the database initialization parameter file (INITSID.ORA). Note: This parameter value should match that of the INSTANCE_NAME parameter.
Global Database Name	GLOBAL_DBNAME	The global database name is the name and domain name of the database as provided by the SERVICE_NAMES parameter in the INITSID.ORA file. If you want to refer to the database by its global database name on the network, then you must specify that global database name to the listener. Note: This parameter value should match the value of the SERVICE_NAMES parameter.
Oracle Home Directory	ORACLE_HOME	The Oracle Home Directory identifies the Oracle Home location of the database that you are specifying. Note: Not required for Windows NT.

To statically configure the listener:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Listeners folder.

3. Click on a listener.

4. Choose Database Services from the drop-down list box:

   
   

5. Modify the fields as appropriate.

6. Select Save Network Configuration from the File menu.

7. Choose Exit from the File menu to exit the Net8 Assistant application.

An excerpt of a LISTENER.ORA file statically configured with the SID_LIST_listener_name section is shown below:

sid_list_listener=(sid_list=
(sid_desc=
 (global_dbname=sales.com)
 (sid_name=db1)
 (oracle_home=/u01/app/oracle/8.1.5)
)

Configuring Prestarted or Prespawned Dedicated Servers

To create prespawned dedicated servers, add the following four parameters in each SID_DESC in the LISTENER.ORA file:

Net8 Assistant Option	LISTENER.ORA Parameter	Description
Maximum Prespawned Servers	PRESPAWN_MAX	The maximum number of prespawned dedicated servers the listener will create. This number must be at least as many as the sum of the pool size for each protocol. Set this value to a large number so that prespawned dedicated servers are always available for new connections.
TCP/IP, SPX, Named Pipes, IPC	PROTOCOL	The protocol on which the listener creates prespawned dedicated servers.
Number	POOL_SIZE	The number of unused prespawned dedicated servers for the listener to maintain on the selected protocol. Choose a number that is greater than 0 but no greater than the PRESPAWN_MAX value. The value should be about what you expect the average number of connections to be at any given time.
Timout	TIMEOUT	Time in minutes that an inactive prespawned dedicated server process waits for the next connection. The value should be greater than 0. (A value of 0 will allow an inactive shadow process to continue indefinitely, thus wasting machine resources.) Set a short time out value. The time out is activated only after a prespawned dedicated server process has carried a connection and been disconnected. In other words, prespawned dedicated servers that are waiting for their first connection do not time out.

To configure prespawned dedicated servers:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Listeners folder.

3. Click on a listener.

4. Choose Database Services from the drop-down list box.

5. Select Use Prespawned Dedicated Servers, and click Configure Prespawned Servers.

6. The Configure Prespawned Servers dialog box appears:

   
   

7. In the Configure Prespawned Servers dialog box, enter appropriate information.

8. Select Save Network Configuration from the File menu.

9. Choose Exit from the File menu to exit the Net8 Assistant application.

An excerpt of a LISTENER.ORA file configured with prespawned dedicated server is shown below:

sid_list_listener=(sid_list=
(sid_desc=
 (global_dbname=sales.com)
 (sid_name=db1)
 (oracle_home=/u01/app/oracle/product/8.1.5)
 (prespawn_max=25)
 (prespawn_list=
  (prespawn_desc=
   (protocol=tcp)
   (pool_size=4)
   (timeout=5)
   )
  )
 )
)

Configuring Protocol Addresses

When a connection is made, the client and the receiver of the request, such as a listener, Oracle Names server, or Oracle Connection Manager, are configured with identical protocol addresses. The purpose of the address is to identify the network address of a network object. The client uses this address to send the connection request to a particular network object location, and the recipient "listens" for requests on this address, and grants a connection based on its address information matching the client information. It is important to install the same protocols for the client and the connection recipient, as well as configure the same address.

This section covers the following topics:

• Address Components

• Protocol Parameters

Address Components

Protocol addresses are contained within the following components:

(address=
 (protocol=tcp)
 (host=sales-pc)
 (port=1521)
)

 (address_list=
  (address=
   (protocol=tcp)
   (host=sales-pc)
   (port=1521)
  )  
  (address=
   (protocol=tcp)
   (host=hr-pc)
   (port=1521)
  ) 
 ) 
 (address_list=
  (address=
   (protocol=tcp)
   (host=finance-pc)
   (port=1521)
  )  
  (address=
   (protocol=tcp)
   (host=sales-pc)
   (port=1521)
  ) 
 ) 

Protocol Parameters

The listener, Oracle Names server and Oracle Connection Manager are identified by protocol addresses. The table below describes the parameters used by the supported Oracle protocols:

Protocol	Parameter	Description
All	PROTOCOL	Indicates the type of network on which the TNS-based application resides.
Bequeath1	PROGRAM	Identifies the Oracle8i executable.
Bequeath	ARGV0	Identifies the service name.
Bequeath	ARGS	Identifies the source of the connection (local client).
IPC	KEY	Indicates a way of identifying the server. Oracle Corporation recommends using the name of the service.
Named Pipes	SERVER	Indicates the name of your Oracle8i server computer.
Named Pipes	PIPE	Indicates the pipe name you use to connect to your server (the same PIPE keyword you specified on server with Named Pipes). This name can be any arbitrary name.
LU6.2	LU_NAME	Identifies the Oracle8i server; must be a fully-qualified name.
LU6.2	LLU or LOCAL_LU	Identifies the local LU alias. This parameter cannot be used with LLU_NAME.
LU6.2	LLU_NAME or LOCAL_LU_NAME	Specifies the local LU name; must be a fully qualified name. This parameter cannot be used with LLU.
LU6.2	MODE or MDN	Identifies the log mode entry of the LU6.2 network; the value is typically ORAPLU62.
LU6.2	PLU or PARTNER_LU_NAME	Identifies the Oracle8i server; must be a fully qualified name.This parameter cannot be used with PLU_LA.
LU6.2	PLU_LA or PARTNER_LU_LOCAL_ALIAS	Identifies the partner LU alias of the Oracle7 Server. This parameter cannot be used with PLU.
LU6.2	TP_NAME or TPN	Identifies the transaction program name of the host machine. This parameter is not required for a connection to an MVS host.
SPX	SERVICE	Defines the name of the TNS-based application on the network. (Mandatory for server and client.) Speak to your network administrator to learn the service names of TNS-based applications on your network.
TCP/IP and TCP/IP with SSL	HOST	Identifies the server.
TCP/IP and TCP/IP with SSL	PORT	Identifies the listening port number: 1521 is the default listening port for client connections to a database service. In future release, this port number may change to the officially registered port number of 2483 for TCP/IP and 2484 for TCP/IP with SSL. 2481 is the recommended and officially registered listening port for client connections to the Java option using TCP/IP. 2482 is the recommended and officially registered listening port for client connections to the Java option using TCP/IP with SSL. 1575 is the default and officially registered listening port for an Oracle Names server using TCP/IP or TCP/IP with SSL. 1630 is the default and officially registered listening port using TCP/IP for the Oracle Connection Manager CMGW gateway process. 1830 is the default and officially registered listening port using TCP/IP for the Oracle Connection Manager CMADMIN administrative process. Note: Oracle Corporation allows port numbers from 1 to 65535, but port numbers less than 1024 are restricted to use by privileged processes on many operating systems.

1 Bequeath requires configuration information in TNSNAMES.ORA but not in LISTENER.ORA.