Oracle Names Administrator's Guide Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents
Go to Index
Index



Go to previous file in sequence Go to next file in sequence

Setting Up and Running Oracle Names with the Dynamic Discovery Option


Oracle Names This chapter describes how to configure a network that uses Oracle Names. If you are using Oracle Names and the Dynamic Discovery Option, you may not need to configure your system at all. See Chapters 1, 2 and 5 for more information.

Also included in this chapter is a section on configuration parameters you can use with the Oracle Names Server once your configuration is complete.

This chapter discusses configuration issues in the following order:


Using Network Manager

Oracle Network Manager is a tool that assists you in creating the configuration files needed for Oracle networking products.

Network Manager allows information that is used across your network in several files to be entered only once, and allows changes in configuration data for one component to "ripple through" and cause changes in other related component information. Network Manager also enables you to use control commands in Oracle Names Control Utility (NAMESCTL).

New to Network Manager is the ability to toggle the Dynamic Discovery Option on or off for individual listeners and Names Servers, and to include a global database name in the LISTENER.ORA file.

Defining Network Objects With Network Manager

There are three major steps to configuring a network using Oracle Network Manager.

These procedures are all described in detail in the Oracle Network Manager Administrator's Guide.


Defining a Names Server

This section briefly covers how to define a Names Server using Network Manager. If you want more information, see Oracle Network Manager Administrator's Guide.

What Can be Defined In a Names Server

The following items can be defined in a Names Server using Network Manager:

Note: Even if you do not select this check box, and thus leave DDO on, the Names Server must be specially configured to act as a well-known Names Server in a DDO network. This configuration must be done manually. See Chapter 5, "Setting Up and Running Oracle Names with the Dynamic Discovery Option".

How to Define a Names Server

Your next step in configuring your network is defining your Names Server.

See the Oracle Network Manager Administrator's Guide for information on how to define a Names Server.


Oracle Names Server Configuration Parameters

This section describes all the configurable parameters that control how Oracle Names Servers operate. These parameters are located in the configuration file NAMES.ORA.

You can control all the parameters for the administrative region the Names Server is in by using Oracle Network Manager. These configuration parameters are either read directly from the network definition database by the Names Server itself, or are read by the client or NAMESCTL, as appropriate.

You typically enter and maintain most of these parameters by using Oracle Network Manager, which places them in the configuration files that it generates.

The configuration files should not be manually edited. All other parameters, including the NAMESCTL parameters, must be added manually. Also, you can only edit configuration files that were generated by Network Manager.

Names Server Parameters

The following, which appear in the NAMES.ORA file, are valid parameters for a Names Server.

names.cache_checkpoint_ file

Specifies the name of the operating system file to which the Names Server writes its checkpoint file. See the Oracle operating system-specific manual for your platform for filename restrictions.

Status:

optional

Type:

text string

Source:

Network Manager enterable field

Default value:

ckpcch.ora

Valid in File:

NAMES.ORA


names.cache_checkpoint_file = filename

names.cache_checkpoint_ interval

Indicates the interval at which a Names Server writes a checkpoint of its stored data to the checkpoint file.

Each Names Server can periodically write its cached data to a file to protect against startup failures. When the Names Server cannot contact the Network Manager database, it starts from the checkpoint file. The default value is 0, or no checkpointing.

Status:

optional

Type:

number (time in seconds)

Source:

Network Manager enterable field

Default value:

0

Valid in File:

NAMES.ORA

Minimum value:

10

Maximum value:

259200 (3 days)

Special value:

0 (disabled)


names.cache_checkpoint_interval = seconds

names.log_directory

Indicates the name of the directory where the log file for Names Server operational events are written. For details on logging see the Oracle Network Products Troubleshooting Guide. For the default name of this file on your system see the Oracle operating system-specific manual for your platform.

Status:

optional

Type:

text string

Source:

Network Manager enterable field

Default value:

platform specific

Valid in File:

NAMES.ORA


names.log_directory = complete_directory_name

names.log_file

Indicates the name of the output file to which Names Server operational events are written. For details on logging see the Oracle Network Products Troubleshooting Guide.

The file name extension is always .log. Do not enter an extension in the Network Manager field for this parameter.

Status:

optional

Type:

text string

Source:

Network Manager enterable field

Default value:

names

Valid in File:

NAMES.ORA


names.log_file = filename

names.log_stats_interval

Specifies the number of seconds between statistical entries in the log file.

Status:

mandatory

Type:

number (time in seconds)

Source:

Network Manager enterable field

Default value:

0 (0 = OFF)

Valid in File:

NAMES.ORA

Minimum Value:

10 (least possible ON value)

Maximum Value:

none


names.log_stats_interval = seconds

names.max_open_ connections

Specifies the number of connections that the Names Server can have open at any given time. The value is generated automatically by Network Manager as the value 10 or the sum of one connection for listening, five for clients, plus one for each foreign domain defined in the local administrative region, whichever is greater.

The calculated value is acceptable for most installations.

Status:

optional

Type:

number

Source:

Generated by Network Manager

Default value:

Calculated based on entered data

Valid in File:

NAMES.ORA

Minimum Value:

2

Maximum Value:

64

names.max_open_connections = number

names.reset_stats_interval

Specifies the number of seconds during which the statistics collected by the Names Servers should accumulate. At the frequency specified, they are reset to zero. The default value of 0 means never reset statistics.

Status:

mandatory

Type:

number (time in seconds)

Source:

Network Manager enterable field

Default value:

0

Valid in File:

NAMES.ORA

Minimum Value:

10

Maximum Value:

none

Special Value:

0 (never reset)


names.reset_stats_interval = seconds

names.server_name

Each Names Server is uniquely identified by a name. All configuration references to a particular Names Server use this name.

Status:

mandatory

Type:

text string

Source:

Network Manager enterable field

Default value:

NameServer.domain_name

Valid in File:

NAMES.ORA


names.server_name = valid_string

names.trace_directory

Indicates the name of the directory to which trace files from a Names Server trace session are written. For details on tracing, see the Oracle Network Products Troubleshooting Guide.

Status:

optional

Type:

text string

Source:

Network Manager enterable field

Default value:

platform specific (for example, names)

Valid in File:

NAMES.ORA


names.trace_directory = complete_directory_name

names.trace_file

Indicates the name of the output file from a Names Server trace session. For details on tracing see the Oracle Network Products Troubleshooting Guide.

The filename extension is always .trc. Do not enter an extension in the Network Manager field for this parameter.

Status:

optional

Type:

text string

Source:

Network Manager list

Default value:

names

Valid in File:

NAMES.ORA


names.trace_file = filename  

names.trace_level

Indicates the level at which the Names Server is to be traced. See the Oracle Network Products Troubleshooting Guide for details on how to initiate tracing.

Status:

optional

Type:

text string

Source:

Network Manager list

Default value:

OFF

Valid in File:

NAMES.ORA


names.trace_level = [OFF|USER|ADMIN]

names.trace_unique

Indicates whether each trace file has a unique name, allowing multiple trace files to coexist. If the value is set to ON, a process identifier is appended to the name of each trace file generated. For details on tracing, see the Oracle Network Products Troubleshooting Guide.

Status:

optional

Type:

text string

Source:

Network Manager list

Default value:

OFF

Valid in File:

NAMES.ORA


names.trace_unique = ON  
names.trace_file = names_05.trc

Sample Names Server Configuration File--NAMES.ORA

Each Names Server in the network requires an individual configuration file called NAMES.ORA. This file contains control parameters for the Names Server and points the Names Server to the database where the network definition is stored.

The following is an example of a NAMES.ORA configuration file:

names.server_name = NameServer.us.oracle.com
names.admin_region = (REGION=
				(NAME= LOCAL_REGION.world)
				(TYPE= ROSDB)
				(USERID= NETADMIN)
				(PASSWORD= netadmin)
				DESCRIPTION=
				 (ADDRESS_LIST=
				  (ADDRESS=
				   (COMMUNITY=TCPCOM.us.oracle.com)
				   (PROTOCOL=TCP)
				   (Host=deer.us.oracle.com)
				   (Port=1521)
				  )
				 )
				 (CONNECT_DATA=(SID=ds)
				 )
				)
				(DOCNAME=deer)
				(VERSION= 34611200)
				(RETRY = 600))
names.config_checkpoint_file= cfg00406
names.trace_level= OFF
names.trace_unique= OFF


Defining Client Profiles

Client profiles are created automatically by Network Manager. For every community created and for every node that is a member of more than one community, Network Manager creates a client profile.

Each client or set of similar clients needs to be assigned a client profile. The complete definition of a client profile includes an intersection of the position of the client in the TNS network, and its relation to the Names Servers in its administrative region. The following two sets of information make up the client profile:

In a flat naming model, when defined by Network Manager, the default domain for all clients is the WORLD domain; that is, all clients and services reside in the WORLD domain. (Without SQLNET.ORA, the default domain is [ROOT] or ".") For example, a global database service name in a flat model might be SALES.WORLD. A global database service name in a hierarchical model might be HR.US.ORACLE.COM.

All clients that belong to the same community, use the same Interchanges, and use the same Names Servers can share a single client profile. Any variation requires a separate client profile.

Client profiles are automatically created for you during the network definition process from information entered into other property sheets. You may want to edit the client profile if you want to designate a Names Server on a particular node as a preferred Names Server.

For more information on client profiles, see the Oracle Network Manager Administrator's Guide.

Client Configuration File--SQLNET.ORA

The following configuration parameters are listed in the client SQLNET.ORA file. You provide these parameters using the Network Manager.

Note: The default domain is not necessarily the domain where the client resides--it could be a domain that the client most often requests network services.


Configuration Parameters For Clients

This section describes all the configurable parameters that control how Oracle Names Servers and their clients operate. Each section includes the filename in which the parameter is valid.

These configuration parameters are either read directly from the network definition database by the Names Server itself, or are read by the client or NAMESCTL, as appropriate.

You typically enter and maintain most of these parameters by using the Oracle Network Manager, which places them in the configuration files that it generates.

The configuration parameters described include those that apply to:

The configuration files should not be manually edited. The exception is the SQLNET.ORA file because Network Manager only provides a few of its possible parameters (including NAMES.PREFERRED_SERVERS, NAMES.DIRECTORY_PATH, and NAMES.DEFAULT_DOMAIN). All other parameters, including the NAMESCTL parameters, must be added manually using the text editor of your choice. Also, you can only edit configuration files that were generated by Network Manager.

Additionally, you can use the configuration parameters on the command line when running the NAMESCTL utility.

Client Parameters

The following client parameters, which appear in the SQLNET.ORA file are valid parameters for a client of Oracle Names.

names.default_domain

Indicates the domain from which the client most often requests names. When this parameter is set to the default domain name (for example, US.ACME), the domain name will be automatically appended to the service name. For example, a client with a default_domain of US.ACME can request a database service named FINANCE.US.ACME as:

sqlplus scott/tiger@FINANCE

All names outside the default domain must be fully specified as global names; for example, FINANCE.US.ACME.

Status:

generated by Network Manager

Type:

text string

Source:

Network Manager enterable field

Default value:

WORLD

Valid in file:

SQLNET.ORA


names.default_domain = <valid domain name>

Note: The Network Manager automatically adds the NAME.DEFAULT_ZONE parameter in addition to the NAMES.DEFAULT_DOMAIN for backward compatibility.

names.preferred_servers

Indicates the Names servers that will be used for a client's name requests. Lists one or more Names Servers in the order they will be used for name requests.

Status:

mandatory

Type:

TNS address

Source:

Network Manager selection list

Valid in file:

SQLNET.ORA

Note: The Network Manager adds the NAMES.PREFERRED_SERVERS parameter to the SQLNET.ORA file for backward compatibility with earlier versions of SQL*Net.

names.preferred_servers = 
	(ADDRESS_LIST = 
		(ADDRESS = 
			(COMMUNITY = community)
			(PROTOCOL = protocol)
			(HOST = hostname)
			(PORT = portnumber)
		)
		(ADDRESS = 
			(COMMUNITY = community)
			(PROTOCOL = protocol)
			(HOST = hostname)
			(PORT = portnumber)
			)
		)
The following example shows the NAMES.PREFERRED_SERVER parameter using a TCP/IP protocol:

name.preferred_servers = 
	(ADDRESS_LIST = 
		(ADDRESS = 
			(COMMUNITY = TCP.HOCKEY)
			(PROTOCOL = TCP)
			(HOST = messier)
			(PORT = 1600)
			)
		)

names.directory_path

Indicates the Names service, such as TNSNames or Oracle Names, that will be used for client name requests.

Status:

mandatory

Type:

TNS address

Source:

Network Manager selection list

Valid in file:

SQLNET.ORA

Note: The Network Manager adds the NAMES.DIRECTORY_PATH parameter to the SQLNET.ORA file for backward compatibility with earlier versions of SQL*Net.

names.directory_path = (naming_service)

such as
names.directory_path = (TNSNAMES, ONAMES)

Sample Configuration File for a Client

Parameters for Oracle Names clients are in the SQLNET.ORA file. A sample of a portion of a SQLNET.ORA file is shown below.

Note: The Network Manager automatically adds the NAMES.PREFERRED_SERVERS and the NAME.DEFAULT_ZONE parameters to the SQLNET.ORA file for backward compatibility with earlier versions of SQL*Net.

TRACE_LEVEL_CLIENT = OFF
names.default_domain = us.oracle.com
names.directory_path = (TNSNAMES, ONAMES)
name.default_zone = us.oracle.com
names.preferred_servers = 
		(ADDRESS_LIST = 
		  (ADDRESS = 
		     (COMMUNITY = TCPCOM.us.oracle.com)
		     (PROTOCOL = TCP)   
		     (Host = doedoe.us.oracle.com)
		     (Port = 1522)
		  )
		  (ADDRESS = 
		     (COMMUNITY = TCPCOM.us.oracle.com)
		     (PROTOCOL = TCP)   
		     (Host = one-eye.us.oracle.com)
		     (Port = 42005)
		  )
		 )
name.preferred_servers = 
		(ADDRESS_LIST = 
		  (ADDRESS = 
		     (COMMUNITY = TCPCOM.us.oracle.com)
		     (PROTOCOL = TCP)
		     (Host = doedoe.us.oracle.com)
		     (Port = 1522)
		)
		  (ADDRESS = 
		     (COMMUNITY = TCPCOM.us.oracle.com)
		     (PROTOCOL = TCP)   
		     (Host = one-eye.us.oracle.com)
		     (Port = 42005)
		  )
		 )

Names Control Utility Parameters

The valid parameters for the Oracle Names Control Utility, or NAMESCTL, are described below. To add any of these parameters to the SQLNET.ORA file, you must use a text editor. For more information on Names Control Utility Parameters, see Appendix A "Oracle Names Control Utility Reference".

namesctl.noconfirm

Indicates whether sensitive changes should be prompted with a confirmation when running the NAMESCTL utility.

Status:

optional

Type:

Boolean

Source:

editable file entry

Default value:

OFF

Valid values:

OFF|ON

Valid in File:

SQLNET.ORA


namesctl.noconfirm = [OFF|ON]

namesctl.trace_level

Indicates the level at which the NAMESCTL program should be traced. Should only be used if NAMESCTL is suspected of causing problems.

Status:

optional

Type:

text string

Source:

editable file entry

Default value:

OFF

Valid values:

OFF|user|admin

Valid in File:

SQLNET.ORA


namesctl.trace_level = [OFF|USER|ADMIN]

namesctl.trace_file

Indicates the file in which the NAMESCTL trace output is placed.

Status:

optional

Type:

text string

Source:

editable file entry

Default value:

namesctl_PID.trc (os -specific)

Valid values:

valid file name (OS specific)

Valid in File:

SQLNET.ORA


namesctl.trace_file = file_name

namesctl.trace_directory

Indicates the directory where trace output from the NAMESCTL utility is placed.

Status:

optional

Type:

text string

Source:

editable file entry

Default value:

none

Valid values:

valid directory name (OS specific)

Valid in File:

SQLNET.ORA


namesctl.trace_directory = /your_directory

namesctl.trace_unique

Indicates whether a process identifier is appended to the name of each trace file generated, so that several can coexist. By default, the value is OFF, which means that when a new trace file is created for the Names Control Utility, it overwrites the existing file.

Status:

optional

Type:

text string

Source:

editable file entry

Default value:

OFF

Valid values:

OFF | ON

Valid in File:

SQLNET.ORA


namesctl.trace_unique = [OFF|ON] 

namesctl.server_password

Indicates the value that matches configured password in the Names Server. This eliminates the need to type the password each time when using the NAMESCTL utility. Note that it should not be used in a shared SQLNET.ORA file because all users would have access to it. Be sure that operating system privileges restrict who can read SQLNET.ORA when using this parameter.

Status:

optional

Type:

text string

Source:

editable file entry

Default value:

PUBLIC

Valid values:

valid password

Valid in File:

SQLNET.ORA


namesctl.server_password = your_password


Defining Global Database Links

A global database link is a link that connects each database in a network to all other databases. This link is created automatically by the Network Manager for use with Oracle Names. Each global database link created by Network Manager connects you to every other database server in the network.

Defining Database Links

When a database service is defined in the Network Manager, a global database link to each database server is automatically created from every other database server in the network. These global database links do not reside in the database's data dictionary, but in the network definition from which the Names Servers loads information. The default global database links created when you define a database service do not include a CONNECT TO clause. This means that users access the linked database using the same usernames and passwords as they used to reach the first database.

For information on configuring global database links in Network Manager, refer to the Oracle Network Manager Administrator's Guide. For more information on configuring and using public and private database links, see Understanding SQL*Net. Also refer to the Oracle7 Server Administrator's Guide.

Specifying Global Links with Username and Password

You can edit global database links to include CONNECT TO data using Network Manager. When you edit a database definition, you can specify a single default username and password for the database link. See the Oracle Network Manager Administrator's Guide for details on how to edit database links.

Note: You can define multiple database links by using connection qualifiers in Network Manager; however, connection qualifiers for public and private database links must be defined locally for each database.

Using Connection Qualifiers to Define Multiple Database Links

Connection qualifiers to a database link (delimited by the second @ sign) provide a means to create multiple links to a database. Multiple database links to the same database provide different access routes with different accounts and privileges. Database link connection qualifiers are used with private, public, and global database links. However, in Network Manager, you can configure connection qualifiers with global database links only.

Note: The connection qualifier username and password configured in Network Manager must match a valid username and password in the target database.

The following examples select data from the same database (HR.US.ORACLE.COM), but use three distinct database links. Each database link accesses different accounts on the same database with a different set of access privileges.

SELECT * FROM emp@hr.us.oracle.com;
SELECT * FROM schedule@hr.us.oracle.com@admin;
SELECT * FROM emp_salaries@hr.us.oracle.com@fin;

In the above example, @admin and @fin are connection qualifiers. Each of the above links could be resolved as a private, public, or Oracle Names (global) database link.

USING Clause No Longer Necessary in Public and Private Links

Unless you want to include a username/password or override the CONNECT TO clause, you do not need to create public or private database links for each local database. In fact, because Oracle Names stores names and addresses, the database string (specified by the USING 'dbstring' clause in the CREATE DATABASE LINK command) is no longer necessary, providing that dbstring is a database name defined in the Names Server.

Restrictions on Global Database Names

When GLOBAL_NAMES = TRUE in a database initialization file, the global database name used in the database link must match the GLOBAL_NAME parameter name of the database it connects to. This helps to ensure that each database link connects to the correct database.

It is recommended that global database names be assigned either when databases are created or when Oracle Names is installed. Thereafter it is recommended that you not change global database names unless absolutely necessary.

SQL*Net requires that all global names be fewer than or equal to 64 characters in length.

Using Aliases For Database Links

Aliases are typically used if a database service or database link must be referred to by more than one name. Aliases can save the administrator from maintaining multiple copies of data just to provide the same service under two names.

Additionally, a network administrator could create aliases so that users can connect to a database or use a database link by using a simple name instead of having to specify the global database name or global database link name (that is, the fully-qualified name). Refer to the Oracle Network Manager Administrator's Guide for information on how to configure service name aliases.




Go to previous file in sequence Go to next file in sequence
Prev Next
Oracle
Copyright © 1996 Oracle Corporation.
All Rights Reserved.
Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents
Go to Index
Index