Oracle Names Administrator's Guide

Library

Product

Contents

Index

Setting Up and Running Oracle Names with the Dynamic Discovery Option

• Using Network Manager
• Defining a Names Server
• Oracle Names Server Configuration Parameters
• Defining Client Profiles
• Configuration Parameters For Clients
• Defining Global Database Links

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:

• How to use Network Manager

• Defining a Names Server

• Defining a client profile

• Defining global database links

Using Network Manager

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

1. Create a network definition using Network Manager property sheets.

2. Generate network component configuration files using the GENERATE command in Network Manager.

3. Distribute the configuration files to the appropriate nodes on the network.

Defining a Names Server

What Can be Defined In a Names Server

• Name of actual Names Server--creates a service name for the Names Server.

If you have more than one Names Server in a domain, each must have a unique name.

• Node

Oracle recommends that if more than one community exists in the network, a Names Server should be placed on the same nodes as the MultiProtocol Interchange so that there is a Names Server available in every community.

• Password--creates a password if you want to require a password of anyone who wishes to manipulate the Name Server.

• Disable Dynamic Discovery--enables/disables DDO.

If you do not want this Names Server to use the DDO, you must select OFF. The default is for DDO to be ON.

• Tuning--sets timing parameters for the Names Server.

• Address--creates an address for the Names Server.

• Logging--changes any of the logging parameters.

• SNMP--enables the Names Server to be monitored using Oracle SNMP Support. You can enter parameters to control the Names Server subagent that is used if Oracle SNMP Support is desired.

How to Define a Names Server

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

Oracle Names Server Configuration Parameters

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

names.cache_checkpoint_ file

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

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

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

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

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

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

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

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

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

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

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

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

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

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:

• community--Each client is defined in terms of what community it belongs to, and which Interchange(s) it prefers to try, in order, when connecting to other communities.

• Oracle Names--Each client is also defined by the default domain it uses, and the list of Names Servers, in order, that should be contacted to resolve global names.

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

• NAMES.PREFFERED_SERVERS--A mandatory list of preferred Names Servers, that is, an ordered list of network addresses to contact when a name must be resolved. The client needs to be able to direct the global name request to a Names Server in the network. Multiple Names Servers should be listed wherever possible for greater reliability when the preferred Names Server is unavailable.

• DEFAULT_DOMAIN--The default domain simplifies access to any service in the client default domain. Each client has a default domain within which service names can be partially qualified. Whenever a name is requested without a "." (period) in it, the default domain is appended to the name before it is forwarded to the Names Server.

• NAMES.DIRECTORY_PATH--This indicates the name resolution service, such as TNSNAMES.ORA or Oracle Names, that will be used for client name requests.

Configuration Parameters For Clients

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:

• Clients that access a Names Server. The second section lists the parameters available to a client accessing a Names Server.

• The Names Control Utility (NAMESCTL)

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

Client Parameters

names.default_domain

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

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

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

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

namesctl.noconfirm

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

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

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

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

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

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

Defining Database Links

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

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

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

Restrictions on Global Database Names

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

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.

Prev Next

Copyright © 1996 Oracle Corporation. All Rights Reserved.

Library

Product

Contents

Index