Files Created by Network Manager
When the network is specified to Network Manager (or a change is made to an existing network definition), a set of SQL*Net configuration files is created on the Windows workstation. Individual directories are created for each client and server node defined in the network. In each of these directories, you’ll find the files shown in Table 5.2.
|
File |
Distributed to |
Description |
|
Client (and server when using database links or distributed processing) |
Contains all service names for all databases and interchanges on the network. | |
|
Client |
Contains parameters to control SQL*Net diagnostics (logging and tracing). | |
|
Client |
Contains a list of local communities in the client profile or node. This file also contains information to identify the location of interchanges for connections across communities. | |
|
Server |
Contains information unique to each server specifying how SQL*Net should configure and operate the TNS (Transparent Network Substrate) listener on the server. | |
|
MultiProtocol Interchange |
Contains parameters to control the operation of a particular MultiProtocol Interchange. | |
|
MultiProtocol Interchange |
Contains information to describe the relationships of all the communities and interchanges in the network. | |
|
Connection Manager |
Contains parameters to control the operation of the Oracle Connection Manager. | |
|
Names Server |
Contains parameters to control the operation of a single Oracle Names server. |
Once these files are created, the DBA must copy the files, using a technique such as FTP or Windows copy, to the appropriate node (identified by the directory name).