Oracle Enterprise Manager Installation 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

Configuration Files

This appendix discusses the configuration files that are required for the Oracle Enterprise Manager and its components. The topics covered are:

Additional Information:
For more information on SQL*Net, network configuration files, and network configuration parameters, see the Understanding SQL*Net, Oracle Network Manager Administrator's Guide, Oracle SNMP Support Reference Guide, and Oracle Network Products Messages Manual.

Configuration Files

The Oracle Enterprise Manager Console uses a daemon process for network communication with the Oracle Intelligent Agents on remote systems. The network communication is done using Oracle's SQL*Net product.

Job Scheduling, Event Management, Software Manager, Data Manager, and Tablespace Manager rely on communication between the Console, agent, and daemon, and require SQL* Net V2.3, which is included as part of the Oracle Enterprise Manager installation.

SQL*Net requires a number of configuration files in order to work. On both the Console and host node, the following files are needed:

On the host node where the Oracle database and agent reside, the following additional files are needed.

On the Console side of the connection, the topology file is required for releases previous to Enterprise Manager 1.3.x and Intelligent Agent 7.3.3. This additional file is needed to populate the Navigator tree if the Intelligent Agent version 7.3.3 is not used with the Navigator Discovery feature.

Note:
For releases previous to Enterprise Manager 1.3.x and Intelligent Agent 7.3.3, Network Manager 3.1 for Windows is used to build the required network configuration files, including the topology.ora file. You can also use the Oracle Topology Generator to create the topology.ora file.

Configuration for Console Machine

The following are examples of the configuration files needed on the machine where the Oracle Enterprise Manager Console is run:

sqlnet.ora

################
# File	name......: sqlnet.ora
# Name..........: tcpcom.world
# Date..........: 13-NOV-95 10:09:52
################
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
SQLNET.EXPIRE_TIME = 0
NAMES.DEFAULT_DOMAIN = world
NAME.DEFAULT_ZONE = world
SQLNET.CRYPTO_SEED = "2418306024240649"
SQLNET.AUTHENTICATION_SERVICES = (ALL)
DAEMON.TRACE_LEVEL = 15
DAEMON.TRACE_MASK = (106)
DAEMON.TRACE_DIRECTORY = c:\orant\network\trace
 Important things to note about this sqlnet.ora is that the domain name is world, which means any service name in tnsnames.ora should have world tagged onto it. Also, the three parameters which start with DAEMON control the tracing of the Daemon process. To switch off tracing set DAEMON.TRACE_LEVEL to the value OFF. Also make sure to change the trace directory to reflect the current ORACLE_HOME.

The above example assumes ORACLE_HOME is set to C:\ORANT. When tracing is switched on, a trace file called daemon.trc appears in the directory specified by the DAEMON.TRACE_DIRECTORY parameter.

tnsnames.ora

################
# Filename......: tnsnames.ora
# Name..........: LOCAL_REGION.world
# Date..........: 13-NOV-95 10:09:52
################
mydb.world = 
  (DESCRIPTION = 
    (ADDRESS_LIST = 
        (ADDRESS = 
          (COMMUNITY = tcpcom.world)
          (PROTOCOL = TCP)
          (Host = myhost)
          (Port = 1526)
        )
    )
    (CONNECT_DATA =
       (SID = mysid)
       (GLOBAL_NAME = mydb.world)
    )
  )
myagent.world = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=myhost)(Port=1748)))
# Addresses of Oracle SNMP Agent. Note this address must match 
# exactly the entry dbsnmp.address in the SNMP.ORA file on the 
# node on which agent is running. There should be no spaces or 
# return characters.
 This example of tnsnames.ora contains the service name mydb.world. This entry details how to connect to the SQL*Net listener running on machine myhost. This listener is listening for connection requests to the database mysid. It also contains the address of the Agent that is running on the machine myhost.

Attention:
It is absolutely necessary for the address of the agent in the tnsnames.ora file on the Console machine exactly match the address of the agent as specified by the DBSNMP.ADDRESS parameter in the snmp.ora file on the agent's machine.

topology.ora

################
# Filename......: topology.ora
# Name..........: tcpcom.world
# Date..........: 13-NOV-95 10:09:52
################
#
# SQL*Net Listeners
mylsnr.world = (ORACLE_LISTENER, myhost)

# Oracle Databases
mydb.world = (ORACLE_DATABASE, myhost, mylsnr.world)
#
# SNMP Agents
myagent.world = (ORACLE_AGENT, myhost)
 This topology.ora file tells the daemon that there are three services on machine myhost:

Important things to note are that mydb.world and myagent.world are service names which need to be resolved into addresses. Address resolution is done using tnsnames.ora; both entries must appear in that file.

Configuration for Remotely Managed Machines

The following are example configuration files for the machine where the Oracle database and the Oracle Intelligent agent run.

sqlnet.ora

################
# Filename......: sqlnet.ora
# Name..........: myhost.world
# Date..........: 13-NOV-95 10:09:52
################
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
SQLNET.EXPIRE_TIME = 0
NAMES.DEFAULT_DOMAIN = world
NAME.DEFAULT_ZONE = world
SQLNET.CRYPTO_SEED = "2418306024240649"
SQLNET.AUTHENTICATION_SERVICES = (ALL)
 The most important thing to note about this sqlnet.ora is that the domain name is world which means any service name in tnsnames.ora should have world tagged onto it.

tnsnames.ora

################
# Filename......: tnsnames.ora
# Name..........: LOCAL_REGION.world
# Date..........: 13-NOV-95 10:09:52
################
mydb.world = 
  (DESCRIPTION = 
    (ADDRESS_LIST = 
        (ADDRESS = 
          (COMMUNITY = tcpcom.world)
          (PROTOCOL = TCP)
          (Host = myhost)
          (Port = 1526)
        )
    )	
    (CONNECT_DATA =
       (SID = mysid)
       (GLOBAL_NAME = mydb.world)
    )
  )
 Note that the address of the Oracle SNMP Agent does not appear in the version of tnsnames.ora on the machine where the agent runs.

listener.ora

################
# Filename......: listener.ora
# Name..........: myhost.world
# Date..........: 13-NOV-95 10:09:52
################
mylsnr =
  (ADDRESS_LIST =
        (ADDRESS=
          (PROTOCOL=IPC)
          (KEY= mydb.world)
        )
        (ADDRESS=
          (PROTOCOL=IPC)
          (KEY= mysid)
        )
        (ADDRESS = 
          (COMMUNITY = tcpcom.world)
          (PROTOCOL = TCP)
          (Host = myhost)
          (Port = 1526)
        )
  )
STARTUP_WAIT_TIME_mylsnr = 0
CONNECT_TIMEOUT_mylsnr = 10
TRACE_LEVEL_mylsnr = OFF
SID_LIST_mylsnr =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = mysid)
      (ORACLE_HOME = /myoraclehome)
      (PRESPAWN_MAX = 10)
    )
  )
 This example of listener.ora defines the listening address for the SQL*Net Listener mylsnr and tells it about the Oracle Database mysid. To start this listener, enter the command:

$ lsnrctl start mylsnr
This command explicitly specifies the name of the SQL*Net listener.

snmp.ora

################
# Filename......: snmp.ora.sample
#################
snmp.visibleservices = (db_name.world, host_name_lsnr.world) 
snmp.index.db_name.world = 1 
snmp.index.host_name_lsnr.world = 2 
snmp.contact.db_name.world = contact_info 
snmp.contact.host_name_lsnr.world = contact_info 
snmp.sid.db_name.world = server_id
snmp.oraclehome.db_name.world=$ORACLE_HOME 
nmi.register_with_names=false
nmi.trace_level = 0 
nmi.trace_mask = (106) 
nmi.trace_directory = $ORACLE_HOME\network\trace 
dbsnmp.address = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=host_name)(PORT=1748))) 
dbsnmp.spawnaddress = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=host_name)(PORT=1754)))
 This snmp.ora example is used by a pre-7.3.3 Intelligent Agent, or a 7.3.3 Intelligent Agent registering with the Names Server. See Agent Configuration for Previous Releases on page 2-3

Configuration for Intelligent Agent

The configuration files, snmp_ro.ora, and snmp_rw.ora, provide configuration parameters for the agent.

snmp_ro.ora

The snmp_ro.ora file is located in $ORACLE_HOME\network\admin on Windows NT platforms. Do not update this read-only file. It contains the following parameters:

SNMP.VISIBLESERVICES = (service_name1, service_name2, ...)
SNMP.SID.service_name = server_id
 
SNMP.ORACLEHOME.service_name = ORACLE_HOME_DIR

snmp_rw.ora

 The snmp_rw.ora is located in $ORACLE_HOME\network\admin on Windows NT platforms. You can modify this read-write file, but this should be done carefully. It contains the following parameters:

SNMP.INDEX.service_name = index_number
SNMP.CONTACT.service_name.world = "contact_info"
 
NMI.REGISTER_WITH_NAMES = FALSE
 
NMI.TRACE_LEVEL = OFF | USER | ADMIN | nn
 
NMI.TRACE_MASK = (nnn)
 
DBSNMP.ADDRESS = (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP) (HOST=host_name) 
(PORT=1748)))
 
DBSNMP.SPAWNADDRESS = (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
(HOST=host_name) (PORT=1754)))
 The 7.3.3 agent requires port address 1748 and 1754. TCP/IP protocol is required to automatically discover services with the 7.3.3 agent.

The following parameters are not automatically generated, but may be added to the file:

SNMP.CONNECT.service_name.USER = user_name
SNMP.CONNECT.service_name.PASSWORD = password
 
SNMP.DBPOLLTIME = nn
 
NMI.TRACE_DIRECTORY = directory
 
NMI.TRACE_FILE = filename
 
NMI.LOG_DIRECTORY = directory
 
NMI.LOG_FILE = filename

services.ora

 The services.ora file is created when the agent starts and is located in $ORACLE_HOME\network\agent on Windows NT platforms. This file contains a list of the services, such as Oracle databases and listeners, on the node where the agent resides. This file is retrieved from the agent by Oracle Enterprise Manager through the Navigator Discovery menu options.

Parameters for snmp*.ora Files

These parameters are used in the snmp_ro.ora and snmp_rw.ora files, the configuration files for the 7.3.3 Intelligent Agent release. These parameters are also used in the snmp.ora file, the primary configuration file for Intelligent Agent releases prior to the 7.3.3 release.

In the following parameters, note these substitutions:

Note:
If .world is used in the sqlnet.ora file, then you must use .world in the snmp.ora, tnsnames.ora, and topology.ora files. For example, service_name.world and host_name_lsnr.world.

SNMP.VISIBLESERVICES = (service_name1.world, service_name2.world, ...)
The name of the services that the agent is monitoring. Each database and each SNMP-manageable service must be listed. For a database, the service name is the name of the database as it appears in the tnsnames.ora file or in the Names Server. The SQL*NET V2 alias is entered here, not the database server instance Id (SID).

SNMP.INDEX.service_name.world = index_number
The unique index number of the service that the agent is monitoring.

SNMP.SID.service_name.world = server_id
The server Id (SID) of the database service that the agent is monitoring.

SNMP.CONNECT.service_name.world.USER = user_name
The username that the subagent uses to connect to the database. The default is dbsnmp. This parameter is optional.

SNMP.CONNECT.service_name.world.PASSWORD = password
The password for the username that is used by the subagent to connect to the database. The default is dbsnmp. This parameter is optional.

SNMP.ORACLEHOME.service_name.world = ORACLE_HOME_DIR
The Oracle home directory of the database. A separate entry is required for each database even if ORACLE_HOME_DIR is the same for all services.

SNMP.CONTACT.service_name.world = "contact_info"
A string containing contact information, such as name, phone number, and email, of the administrator responsible for the service. This parameter is optional.

SNMP.DBPOLLTIME = nn
The time interval (seconds) that the agent polls the database to check whether it is down. If the database has gone down or was never connected, this is the interval between retries. The default is 30 seconds.

NMI.TRACE_LEVEL = OFF | USER | ADMIN | nn
Turns on tracing at the specified level. Oracle recommends that you set the trace level to 13. Level 15 produces a deluge of information, which is only useful if a bug is being investigated. This parameter is optional.

NMI.TRACE_MASK = (nnn)
Masks the tracing output. This parameter is optional. The mask setting is only relevant in conjunction with nmi.trace_level. Note that (106) causes only trace information for the agent to appear.

NMI.TRACE_DIRECTORY = directory
Directory where trace file is written. The setting is only relevant in conjunction with nmi.trace_level. If omitted, trace files are written to $ORACLE_HOME\network\trace. This parameter is optional.

NMI.TRACE_FILE = filename
Filename of the trace file. This parameter is optional.

NMI.LOG_DIRECTORY = directory
Directory where log file is written. This parameter is optional.

NMI.LOG_FILE = filename
Filename of the log file. This parameter is optional. On Windows NT, the filename defaults to dbsnmp.

NMI.REGISTER_WITH_NAMES = TRUE|FALSE
Determines whether the agent is registered with the Names Server. If the parameter is set to TRUE, the agent automatically attempts to register with the Names Server when it is started. The agent executes namesctl to register with the Names Server. Set this parameter to FALSE if you do not want to run namesctl.

DBSNMP.ADDRESS = (DESCRIPTION=(ADDRESS=(PROTOCOL=protocol) (HOST=host_name)(PORT=port_no)))
The TNS address that the agent uses to listen for incoming requests. There should be no space or return characters in the address. This parameter is the address that the Agent listens on for network connections.

TCP/IP is the only protocol supported by Oracle. TCP/IP is required to automatically discover services with the 7.3.3 agent.

The 7.3.3 agent requires PORT=1748. The port address 1748 is a registered TCP port granted to Oracle by the Internet Assigned Number Authority (IANA). Changing this port makes the agent undetectable by the Enterprise Manager Console and forces a manual configuration setup.

For agent releases previous to the 7.3.3 release, this address must match exactly the entry for this agent in the tnsnames.ora file on the machine where the Oracle Enterprise Manager Console resides.

DBSNMP.SPAWNADDRESS = (DESCRIPTION=(ADDRESS= (PROTOCOL=protocol) (HOST=host_name)(PORT=spnport_no)))
The TNS address which the agent can use to accept RPC's. This address is used for file transfers. The spnport_no used in this parameter is different than port_no used in the DBSNMP.ADDRESS parameter.

The 7.3.3 agent PORT=1754. The port address 1754 is a registered TCP port granted to Oracle by the Internet Assigned Number Authority (IANA). Changing this port makes the agent undetectable by the Enterprise Manager Console and forces a manual configuration setup.

Network Topology Generator

For users with an existing SQL*Net installation and an intelligent agent prior to the 7.3.3 release, the Oracle Network Topology Generator is provided. You should use the Network Topology Generator if you have an existing SQL*Net installation without the SQL*Net configuration tool, Network Manager 3.1.

With the Network Topology Generator, you can:

Creating a New topology.ora File

1.
To start the Network Topology Generator, double-click on its icon in the Oracle Enterprise Manager program group.
The Input File Type dialog box displays. By default, the tnsnames.ora file is selected.
Attention:
The Network Topology Generator can only read a tnsnames.ora or a topology.ora file.

2.
Click OK. The SQL*Net Services Name List appears with the current configuration parameters taken from the tnsnames.ora file. You can click on the Browse button to bring up a standard File Open dialog box to search for a tnsnames.ora file if the utility cannot find the file.
Note:
If any of the generated entries are incorrect, you need to modify them. See the following section, "Editing an Existing topology.ora File."

3.
Click on the Write File button. The Save As dialog box displays with a default filename topology.ora filled in.
4.
Click OK to create the new topology.ora file.
5.
Click Exit to exit the Topology Generator.

Editing an Existing topology.ora File

 The Network Topology Generator also allows you to modify your topology.ora file. You can easily add new entries, edit or delete existing entries.

Adding New Entries

1.
Double-click on the Network Topology Generator icon in the Oracle Enterprise Manager program group.
2.
Select topology.ora from the Input File dialog box. The Service Name List appears.
3.
Click on the Create button. The Network Service Details dialog box appears.
4.
Enter a new service name in the Name entry field.
5.
Select a Service Type from the drop down menu. By default ORACLE_DATABASE is selected.
6.
Enter a new node name.
7.
Enter a new listener name using the format:
LISTENER_node name.domain name
8.
Click OK. The new entry appears in the Service Name column list.
9.
Click on the Write File button to display the Save As dialog box. By default, topology.ora is entered in the File Name field.
Warning:
Although the Network Topology Generator allows you to save your modification to any filename, this utility can only output topology.ora file format. Be careful not to overwrite the tnsnames.ora file.

10.
Click OK.
Warning:
When you save a file using the default topology.ora filename, the existing topology.ora file is overwritten with a new file containing the modifications. The old topology file is not appended.

Modifying Existing Entries

To edit an existing entry, select an entry from the Service Name list and click on the Edit button. The Network Service Details dialog box appears with all fields active except the Service Name. Enter the desired parameters and click OK. From the Service Name List dialog box, click the Write button to create a new topology.ora file.

Deleting Entries

To delete an existing entry, select an item from the Service Name list and click on the Delete button. Click on the Write button to create a new topology.ora file.


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