Release 1.4.0
A53700_01
 Library |
 Product |
 Contents |
 Index |
| Oracle Enterprise Manager Configuration Guide Release 1.4.0 A53700_01 |
|
This appendix discusses the configuration files that are required for the Oracle Enterprise Manager and its components.
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 Net8 product.
Job Scheduling, Event Management, Software Manager, Data Manager, Backup Manager, and Tablespace Manager rely on communication between the Console, agent, and daemon, and require Net8 Assistant.
Net8 Assistant requires a number of configuration files in order to work.
snmp_ro.ora and snmp_rw.ora are created by the Intelligent Agent.
listener.ora is required if a database is on the node. An agent can be installed on a machine without a database.
On both the Console and host node, the sqlnet.ora file, which contains items such as domain name and trace level, is needed:
On the host node where the Oracle database and agent reside, the following additional files are needed.
Contains the listening addresses of the Net8 Listener on the machine plus the name and ORACLE_HOME of any databases the listener knows about.
Contains the listening address of the agent, the names of Net8 listener and Oracle database services it knows about, plus tracing parameters. snmp_ro.ora and snmp_rw.ora are created by the 8.0.3 Intelligent Agent. snmp.ora is used by pre-8.0.3 machines. For information on this file, see Parameters for snmp*.ora Files on page A-7.
On the Console side of the connection, the topology file is required for releases previous to Enterprise Manager 1.3.x and Intelligent Agent 8.0.3. This additional file is needed to populate the Navigator tree if the Intelligent Agent version 8.0.3 is not used with the Navigator Discovery feature.
The following are examples of the configuration files needed on the machine where the Oracle Enterprise Manager Console is run:
################
# 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\net80\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.
################
# 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)
)
)
The following are some of the example configuration files which may be needed for the machine where the Oracle database and the Oracle Intelligent agent run.
################
# 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.
################
# 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)
)
)
################
# 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 Net8 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 Net8 listener.
################
# 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\net80\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-8.0.3 Intelligent Agent, or a 8.0.3 Intelligent Agent registering with the Names Server. Pre-8.0.3 Intelligent Agents can use any port number, as long as the numbers match the tnsnames.ora entries for the Agent.
The configuration files, snmp_ro.ora, and snmp_rw.ora, provide configuration parameters for the agent. These files are created by the 8.0.3 Intelligent Agent.
The snmp_ro.ora file is located in $ORACLE_HOME\net80\admin on Windows NT platforms. This file is located in $ORACLE_HOME/net80/admin on UNIX. 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
The snmp_rw.ora is located in $ORACLE_HOME\net80\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 8.0.3 agent requires port address 1748 and 1754. TCP/IP protocol is required to automatically discover services with the 8.0.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
The services.ora file is created when the agent starts and is located in $ORACLE_HOME\net80\agent on the Windows NT platform and $ORACLE_HOME/net80/agent on UNIX. 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.
These parameters are used in the snmp_ro.ora and snmp_rw.ora files, the configuration files for the 8.0.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 8.0.3 release.
In the following parameters, note these substitutions:
tnsnames.ora.
If .world is used in the sqlnet.ora file, then you must use .world in the snmp.ora and tnsnames.ora files. For example, service_name.world and host_name_lsnr.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 unique index number of the service that the agent is monitoring.
The server Id (SID) of the database service that the agent is monitoring.
The username that the subagent uses to connect to the database. The default is dbsnmp. This parameter is optional.
The password for the username that is used by the subagent to connect to the database. The default is dbsnmp. This parameter is optional.
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.
A string containing contact information, such as name, phone number, and email, of the administrator responsible for the service. This parameter is optional.
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.
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.
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.
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\net80\trace. This parameter is optional.
Filename of the trace file. This parameter is optional.
Directory where log file is written. This parameter is optional.
Filename of the log file. This parameter is optional. On Windows NT, the filename defaults to dbsnmp.
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 8.0.3 agent.
The 8.0.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 8.0.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.
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 8.0.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.
