CRITICAL SKILL 4.8 Use Profiles

Team Fly

Page 154

CRITICAL SKILL 4.8
Use Profiles

A profile contains a set of parameters that define Oracle Net options on the remote or database server. Profiles are stored in the sqlnet.ora file and can be used to

Route connections to specific processes

Control access through protocol-specific parameters

Prioritize naming methods

Control logging and tracing features

Configure for external naming

Define how the client domain should append to unqualified names

During installation, the priority order for the naming methods will be defined. If the first naming method cannot resolve the connect identifier, the next naming method will be checked. The results will then be stored in the sqlnet.ora file, as shown in the following example:

NAMES.DIRECTORY_PATH=(ezconnect, tnsnames)

After installation, Oracle Net Manager can be used to modify the sqlnet.ora configuration file.

Control Access

The sqlnet.ora file can be used to grant or deny access to the Oracle database server. Table 4-7 displays sqlnet.ora parameters that control access.

sqlnet.ora Parameter Name	Description
TCP.VALIDNODE_CHECKING	Determines where to control access to the database. If this parameter is set, the following parameters will be used to define the access.
TCP.EXCLUDED_NODES	Defines which systems are denied access to the database.
TCP.INVITED_NODES	Defines which systems are granted access to the database.
TABLE 4-7. sqlnet.ora Parameters

Team Fly