Oracle7 Administrator's Reference for UNIX

Contents Index Home Previous Next

Configuring SQL*Net Version 2

This section describes the procedures for configuring and using SQL*Net version 2 and the MultiProtocol Interchange.

See Also: The SQL*Net Administrator's Guide for more information on configuration tasks.

Attention: You must configure your network using the netman program in a Windows environment.

Simple SQL*Net Version 2 Installation

A community is a group of machines that use the same transport level protocol. Perform the following steps to set up a community:

	$ telnet hostname

	$ lsnrctl status

	$ sqlplus scott/tiger@finance

Multiple Communities Using an Interchange

Perform the following steps to set up a configuration for an interchange:

	% sqlplus SYS/password@network_alias

SQL*Net Version 2 Configuration File Summary

Table 9 - 1 and Table 9 - 2 show the functions of the configuration, log, trace and navigation files for SQL*Net version 2 and the MultiProtocol Interchange.

Use the Network Manager to create the following files and place them in $ORACLE_HOME/network/admin.

SQL*Net v2 File Purpose Required by Numbers of Copies
tnsnames.ora Lists connect descriptors and aliases that connect network applications. Applications and clients connected to the server. If Oracle Names is used, this file is not required. At least one file. Only one file is used a time.
listener.ora Defines listening endpoints for the SQL*Net Listener. It defines listener DBA-task passwords and mappings of ORACLE SIDs to ORACLE_HOME directories. The SQL*Net Listeners At least one file. Only one is in use at a time.
names.ora Defines control parameters for the Names server. It points to the file that holds service names and addresses of network services. Names servers At least one file for each Names server.
sqlnet.ora Contains logging and tracing diagnostic parameters for clients. It specifies diagnostics and client information about Names servers. It may contain parameters added with a text editor. Clients At least one file for each client and node.
Table 9 - 1. SQL*Net Version 2 Files



Interchange File Purpose Required by Numbers of Copies
intchg.ora Lists parameters for control and definition of interchange features. Every interchange at startup One copy for each interchange.
tnsnet.ora Defines a network layout. It identifies interchanges and communities, and their relations. Use it to choose between paths. Every interchange to perform navigation One copy shared by or copied to all navigators.
tnsnav.ora Defines how navigation occurs for a node. It defines the navigator's address. Clients and interchanges (to identify navigation options). Navigators require it to define its listener addresses. One copy for each navigator. Clients can share copies if they have identical network needs.
Table 9 - 2. Interchange Files


Contents Index Home Previous Next