11
Configuring Profiles

This chapter describes how to configure client and server configuration parameters in profiles. A profile is a collection of parameters that specifies preferences for enabling and configuring Oracle Net features on the client or database server. A profile is stored and implemented through the sqlnet.ora file.

This chapter contains these topics:

• Profile Configuration Overview
• Configuring Client Attributes for Names Resolution
• Configuring Database Access Control
• Configuring Advanced Profile Information
• Configuring Preferred Oracle Names Servers
• Configuring External Naming Methods
• Configuring Oracle Advanced Security

Profile Configuration Overview

You can use a profile to:

• Specify the client domain to append to unqualified names
• Prioritize naming methods
• Enable logging and tracing features
• Route connections through specific processes
• Configure parameters for external naming
• Configure Oracle Advanced Security
• Use protocol-specific parameters to restrict access to the database

Profile Configuration During Installation

Oracle Universal Installer launches Oracle Net Configuration Assistant after software installation on the client and server. Oracle Net Configuration Assistant configures the following:

• Default network domain

  The computer's network domain is automatically selected as the default domain. This domain is appended to any unqualified net service name given in the connect string, and then compared to net service names stored in a tnsnames.ora file or Oracle Names server. For example, if the client tnsnames.ora file contains a net service name of sales.us.acme.com, the user can enter the following connect string:

  CONNECT scott/tiger@sales
  
  

  sales gets searched as sales.us.acme.com.

• The order of the naming methods the computer will use to resolve a connect identifier to a connect descriptor

Configuration with the Oracle Net Configuration Assistant during installation results in the following entries in the sqlnet.ora file:

NAMES.DEFAULT_DOMAIN=us.acme.com
NAMES.DIRECTORY_PATH=(onames, tnsnames)

NAMES.DEFAULT_DOMAIN specifies the network domain, and NAMES.DIRECTORY_PATH specifies the priority order of the naming methods to use to resolve connect identifiers.

If the installed configuration is not adequate, you can use Oracle Net Manager to enhance the sqlnet.ora configuration.

Configuring Client Attributes for Names Resolution

The following sections describe available client configuration options:

• Configuring a Default Domain for Clients
• Prioritizing Naming Methods
• Routing Connection Requests

Configuring a Default Domain for Clients

In environments where the client often requests names from a specific domain, it is appropriate to set a default domain in the client sqlnet.ora file with the NAMES.DEFAULT_DOMAIN parameter.

When a default domain is set, it is automatically appended to any unqualified net service name given in the connect string, and then compared to net service names stored in a tnsnames.ora file or Oracle Names server.

For example, if the client tnsnames.ora file contains a net service name of sales.us.acme.com, the user can enter the following connect string:

CONNECT scott/tiger@sales

In this example, sales gets searched as sales.us.acme.com.

If the connect string includes the domain extension, such as in CONNECT scott/tiger@sales.us.acme.com, the domain is not appended. If a net service name in a tnsnames.ora file or Oracle Names server is not domain qualified and this parameter is set, the net service name must be entered with a dot ("."). For example, if domain is set to us.acme.com and the client tnsnames.ora file contains a net service name of sales, the user would enter the following connect string:

CONNECT scott/tiger@sales.

To specify a default domain:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager"

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select Naming.
4. Click the Oracle Names tab.
5. In the Default Domain field, enter the domain.
6. Choose File > Save Network Configuration.

   The sqlnet.ora file should contain an entry that looks like the following:

   NAMES.DEFAULT_DOMAIN=us.acme.com
   

Prioritizing Naming Methods

After naming methods are configured, as described in Chapter 9, "Configuring Naming Methods", they must be prioritized. The naming method at the top of the list is used first to resolve a connect identifier. If the first naming method in the list is unable to resolve the connect identifier, then the second method in the list is used.

To specify the order of naming methods:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager"

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select Naming.
4. Click the Methods tab.

   Table 11-1 describes the naming method values listed in the Methods tab.

   Table 11-1  Naming Method Values

   Naming Method Value	Description
   TNSNAMES local naming method	Set to resolve a net service name through the tnsnames.ora file on the client. See Also: "Configuring the Local Naming Method"
   LDAP directory naming method	Set to resolve a database service name, net service name, or net service alias through a directory server. See Also: "Configuring the Directory Naming Method"
   ONAMES Oracle Names method	Set to resolve net service names or database service names through a Oracle Names server. See Also: "Configuring the Oracle Names Method"
   HOSTNAME host naming method	Set to resolve a host name alias through an existing names resolution service or a centrally-maintained set of /etc/hosts files. See Also: "Configuring the Host Naming Method"
   CDS Cell Directory Services (CDS) external naming method	Set to resolve an Oracle database name in a Distributed Computing Environment (DCE) environment. See Also: Oracle Advanced Security Administrator's Guide
   NIS Network Information Service (NIS) external naming method	Set to resolve service information through an existing NIS. See Also: "Network Information Service (NIS)"

5. Select naming methods from the Available Methods list, and then click the right-arrow button.

   The selected naming methods move to the Selected Methods list.

6. Order the naming methods according to the order in which you want Oracle Net to try to resolve the net service name or database service name. Select a naming method in the Selected Methods list, and then click Promote or Demote to move the selection up or down in the list.

7. Choose File > Save Network Configuration.

   The sqlnet.ora file updates with the NAMES.DIRECTORY_PATH parameter:

   NAMES.DIRECTORY_PATH=(ldap, tnsnames)
   

Routing Connection Requests

Clients and servers acting as clients can be configured so connection requests are directed to a specific process at all times. Table 11-2 describes the sqlnet.ora file settings that you can set to route connection requests.

Table 11-2  Routing Settings in sqlnet.ora

Oracle Net Manager Option	sqlnet.ora File Parameter	Description
Always Use Dedicated Server	USE_DEDICATED_SERVER	Use to force the listener to spawn a dedicated server for all network sessions from this client. It does this by adding (SERVER=dedicated) to the CONNECT_DATA section of connect descriptors. Connections from this client use dedicated servers, even if shared server is configured.
Prefer Connection Manager Routing	USE_CMAN	Use to send the client to an Oracle Connection Manager whenever possible. If no Oracle Connection Manager protocol addresses are available, connections are routed through any available listener protocol address. Note: If you are using Oracle Connection Manager with Oracle Names, this option must be set on clients and Oracle Names servers.

To route connection requests:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager"

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select General.
4. Click the Routing tab.
5. Select the preferred way that you want connection requests routed.

   See Also: Table 11-2 for a description of the fields and options

6. Choose File > Save Network Configuration.

Configuring Database Access Control

You can configure the sqlnet.ora file to allow access to some clients and deny access to others. Table 11-3 describes the available settings.

Table 11-3  Access Control Settings in sqlnet.ora

Oracle Net Manager Field/Option	sqlnet.ora File Parameter	Description
Check TCP/IP client access rights	TCP.VALIDNODE_CHECKING	Use to specify whether to screen access to the database. If this field is selected, Oracle Net Manager checks the parameters TCP.EXCLUDED_NODES and TCP.VALIDNODE_CHECKING to determine which clients to allow access to the database. If this field is deselected, Oracle Net Manager does not screen clients.
Clients excluded from access	TCP.EXCLUDED_NODES	Use to specify which clients using the TCP/IP protocol are denied access to the database.
Clients allowed to access	TCP.INVITED_NODES	Use to specify which clients using the TCP/IP protocol are allowed access to the database.

To configure database access control:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager" on page 5-3

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select General.
4. Click the Access Rights tab.
5. Select the Check TCP/IP client access rights option.
6. In the Clients excluded from access and Clients allowed to access fields, enter either a host name or an IP address for a client that you wish to include or exclude, using commas to delimit entries placed on the same line.

Configuring Advanced Profile Information

Table 11-4 describes the advanced sqlnet.ora file settings that you can set.

Table 11-4  Advanced Settings in sqlnet.ora

Oracle Net Manager Field/Option	sqlnet.ora File Parameter	Description
TNS Time Out Value	SQLNET.EXPIRE_TIME	Use to specify a specify the time interval, in seconds, to send a probe to verify that client/server connections are active. Setting a value greater than 0 ensures that connections are not left open indefinitely, due to an abnormal client termination. If the probe finds a terminated connection, or a connection that is no longer in use, it returns an error, causing the server process to exit. This setting is intended for the database server, which typically handles multiple connections at any one time. Limitations on using this terminated connection detection feature are: It is not allowed on bequeathed connections. Though very small, a probe packet generates additional traffic that may downgrade network performance. Depending on which operating system is in use, the server may need to perform additional processing to distinguish the connection probing event from other events that occur. This can also result in downgrading network performance.
Client Registration ID	SQLNET.CLIENT_REGISTRATION	Use to specify a unique identifier for a client. This identifier is passed to the listener with any connection request. The identifier can be any string up to 128 characters long.
Turn Off UNIX Signal Handling	BEQUEATH_DETACH	Use to turn on or off UNIX signal handling. Since the client application spawns a server process internally through the Bequeath protocol as a child process, the client application becomes responsible for cleaning up the child process when it completes. When the server process completes its connection responsibilities, it becomes a defunct process. Signal handlers are responsible for cleaning up these defunct processes. Setting this parameter configures the client profile to pass this process to the UNIX init process by disabling signal handlers.
Disable Out-of-Band Break	DISABLE_OOB	Use to turn on or off out of band breaks. If deselected or set to off, enables Oracle Net to send and receive "break" messages using urgent data provided by the underlying protocol. If selected or set to on, disables the ability to send and receive "break" messages using urgent data provided by the underlying protocol. Once enabled, this feature applies to all protocols used by this client. See Also: Oracle operating system-specific documentation to determine if the protocol supports urgent data requests. TCP/IP is an example of a protocol that supports this feature.

To set advanced features for clients:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager"

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select General.
4. Click the Advanced tab.
5. Enter the values for the fields/options you want to set.

   See Also: Table 11-4 for a description of the fields and options

6. Choose File > Save Network Configuration.

Configuring Preferred Oracle Names Servers

If you are using Oracle Names as a naming method, you can specify the name and address of preferred Oracle Names servers to take precedence over any other available Oracle Names server addresses. Oracle Net routes name resolution requests to each preferred Oracle Names Server until a response is received.

Preferred Oracle Names servers are an alternative to using the Discover Oracle Names Servers command in Oracle Net Manager or using the Oracle Names Control utility REORDER_NS command. These commands create a list of Oracle Names servers based on what is available throughout the network and ranks them in the order of fastest response time. Preferred Oracle Names servers override any other Oracle Names servers found during the discovery process. Once you have initially discovered an Oracle Names server, you may want to delete preferred Oracle Names servers.

To specify a preferred Oracle Names server:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager"

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select Preferred Oracle Names Servers.
4. Click New.

   A Preferred Server tab appears.

5. Choose the protocol and enter the requested protocol address information for an Oracle Names server configured on that protocol address.

   See Also: Oracle9i Net Services Reference Guide for protocol parameter settings

6. Repeat Steps 4 and 5 for each additional Oracle Names server you want added to the list.
7. Choose File > Save Network Configuration.

   The sqlnet.ora file updates with the NAMES.PREFERRED_SERVERS parameter:

   NAMES.PREFERRED_SERVERS=
     (ADDRESS=(PROTOCOL=tcp)(HOST=namesrv1)(PORT=1575))
   

Configuring External Naming Methods

Configure required client parameters needed for the NIS external naming or the CDS external naming method in the profile. Table 11-5 describes the sqlnet.ora file external naming settings that you can set.

Table 11-5  External Naming Methods Settings in sqlnet.ora

Oracle Net Manager Field	sqlnet.ora File Parameter	Description
Cell Name	NAMES.DCE.PREFIX	Enter a valid DCE cell name (prefix).
Meta Map	NAMES.NIS.META_MAP	Specify the map, a special file that contains the database service name.

To configure external naming method parameters:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager"

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select Naming.
4. Enter a value in the appropriate field for the external naming method you are using.
5. Choose File > Save Network Configuration.

Configuring Oracle Advanced Security

Oracle Advanced Security enables data encryption and integrity checking, enhanced authentication, single sign-on, and support for DCE. Oracle Advanced Security also provides centralized user management on LDAP-compliant directory servers and certificate-based single sign-on; this functionality relies on the Secure Sockets Layer (SSL).

To configure a client or server to use Oracle Advanced Security features:

1. Start Oracle Net Manager.

   See Also: "Starting Oracle Net Manager"

2. In the navigator pane, expand Local > Profile.
3. From the list in the right pane, select Oracle Advanced Security.

   Each Oracle Advanced Security tab page enables you to configure a separate set of parameters.

   See Also: Choose the Help button on the particular tab page Oracle Advanced Security procedural topics in the Oracle Net Manager online help. To access these topics in the online help, choose Oracle Advanced Security > How To. Oracle Advanced Security Administrator's Guide for further information about configuration

4. Select or edit options as applicable.

5. Choose File > Save Network Configuration.