Release 8.1.5
A67825-01
 Library |
 Product |
 Contents |
 Index |
| Oracle Intelligent Agent Users Guide Release 8.1.5 A67825-01 |
|
This appendix discusses the configuration files that are required for the Oracle Enterprise Manager and its components.
The Oracle Enterprise Manager Console uses SQL*Net for network communication with the Oracle Intelligent Agents on local or remote systems.
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-AUG-97 10:09:52
################
AUTOMATIC_IPC = OFF
TRACE_LEVEL_CLIENT = OFF
SQLNET.EXPIRE_TIME = 0
NAMES.DEFAULT_DOMAIN = world
NAME.DEFAULT_ZONE = world
SQLNET.CRYPTO_SEED = "2418306024240649"
SQLNET.AUTHENTICATION_SERVICES = (NONE)
DAEMON.TRACE_LEVEL = 16
DAEMON.TRACE_DIRECTORY = c:\orant\network\trace
Important things to note about this sqlnet.ora example is that the domain name is world, which means that in this example, any service name in tnsnames.ora should have world tagged onto it.
|
Note: "world" is used as an example of a domain name. You may use your own domain name instead of "world." |
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\NET80\TRACE.
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. Tracing is useful to set up when debugging the console's operations include discovery, jobs, and events status.
################
# Filename......: tnsnames.ora
# Name..........: LOCAL_REGION.world
# Date..........: 13-AUG-97 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 standard locations of the tnsnames.ora file are: $ORACLE_HOME/network/admin or $ORACLE_HOME/net80/admin. On Solaris the tnsnames.ora file can be located in the /var/opt/oracle directory. On other UNIX systems, the tnsnames.ora file can be located in the /etc directory. On all platforms, you can set a $TNS_ADMIN environment variable if you do not want to use any of the default locations.
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-AUG-97 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)
Important things to note about this sqlnet.ora is that the domain name is world in this example, which means that in this example, any service name in tnsnames.ora should have world tagged onto it.
|
Note: "world" is used as an example of a domain name. You may use your own domain name instead of "world." |
################
# Filename......: tnsnames.ora
# Name..........: LOCAL_REGION.world
# Date..........: 13-AUG-97 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-AUG-97 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)
)
)
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 on UNIX, enter the command:
$ lsnrctl start mylsnr
This command explicitly specifies the name of the SQL*Net listener. If you are using the default listener name, you do not need to specify the name when starting the listening process. (The default listener name is "listener.") However, in this example, the listener's name has been changed to "mylsnr." Since this is not the default name, it must be specified during startup.
################
# Filename......: snmp.ora.sample
#################
snmp.visibleservices = (mydb_name.world, myhost_name_mylsnr.world)
snmp.index.mydb_name.world = 1
snmp.index.myhost_name_mylsnr.world = 2
snmp.contact.mydb_name.world = contact_info
snmp.contact.myhost_name_mylsnr.world = contact_info
snmp.sid.mydb_name.world = server_id
snmp.oraclehome.mydb_name.world=$ORACLE_HOME
nmi.register_with_names=false
nmi.trace_level = 0
nmi.trace_directory = $ORACLE_HOME\network\trace
dbsnmp.address = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=myhost_ name)(PORT=1748)))
dbsnmp.spawnaddress = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=myhost_ name)(PORT=1754)))
This snmp.ora example is used by a pre-7.3.3 Intelligent Agent. Pre-7.3.3 Intelligent Agents can use any unused port number, as long as the numbers match the tnsnames.ora entries for the Agent. snmp.ora should be created by the Oracle Network Manager or Topology Generator.
The configuration files, snmp_ro.ora, and snmp_rw.ora, provide configuration parameters for the 7.3.3 (and later) agent. These files are created automatically by the 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/network/admin on UNIX. Do not update this read-only file. It contains the following parameters:
SNMP.VISIBLESERVICES = (LISTENER, 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 = unique_index_number SNMP.CONTACT.service_name.world = "contact_info" NMI.REGISTER_WITH_NAMES = FALSE NMI.TRACE_LEVEL = OFF | USER | ADMIN | nn
Agents, versions 7.3.3 and later, require port address 1748 and 1754. TCP/IP protocol is required to automatically discover services with the agent. The port address is automatically set.
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 DBSNMP.IPCTIME = 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/network/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 configuration files for the 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 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 index number can be any number. The only limitation is that if you have more than one index line, the index numbers must be unique. For example:
snmp.index.<service_name1>=10 snmp.index.<service_name2>=20
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 catsnmp.sql script should be edited and reexecuted if this parameter is not the default setting.
The "subagent" refers to the Intelligent Agent. Sometimes, the Intelligent Agent is called a subagent to the master SNMP agent when configuring SNMP on a server. However, SNMP does not have to be configured on the server before the Intelligent Agent will work (except for the Netware platform). For security reasons, the customers sometimes do not want to use the default Intelligent Agent database account/password of dbsnmp/dbsnmp. The example listed should only be used if they want to change the Intelligent Agent's database logon account.
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 catsnmp.sql script should be edited and reexecuted if this parameter is not the default setting.
The "subagent" refers to the Intelligent Agent. Sometimes, the Intelligent Agent is called a subagent to the master SNMP agent when configuring SNMP on a server. However, SNMP does not have to be configured on the server before the Intelligent Agent will work (except for the Netware platform). For security reasons, the customers sometimes do not want to use the default Intelligent Agent database account/password of dbsnmp/dbsnmp. The example listed should only be used if they want to change the Intelligent Agent's database logon account.
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.
The time interval (seconds) that the agent's Work process pings its Comm process to check whether it is down. If Comm is unable to respond to Work's ping within this time, Work will kill the old Comm process and spawn a new one. Users can lengthen the interval if they want to be able to run long events, separately from the database-checking interval. The default is 30 seconds.
This parameter is not pertain to the NT port of the agent.
Turns on tracing at the specified level. Oracle recommends that you set the trace level to 13. Level 16 produces a deluge of information, which is only useful if a bug is being investigated. With a level of 16, you can see actual TCP/IP packet contents. With a level of 15, I can only see that packets are being passed. This parameter is optional.
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.
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.
|
Note: The following addresses are automatically set by the agent. Changing the addresses makes the agent undetectable by the Enterprise Manager Console and forces a manual configuration setup. |
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 must be installed on the server since it is required to automatically discover services with the agent.
The agent requires PORT=1748. The port address 1748 is a registered TCP port granted to Oracle by the Internet Assigned Number Authority (IANA). The port address is automatically set. 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.
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 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.
