If a node has more than one service, the SNMP.ORA file includes information for all of them. For example, the SNMP.ORA file for a particular node might contain information so that an Interchange and a Names Server can respond to SNMP queries from an SNMP-based network management system. Or, an SNMP.ORA file on a particular node might include parameters for a listener and a database only.
The sample SNMP.ORA file in this section enables SNMP support for five services including a listener, two databases (HR.WORLD and SALES.WORLD), an Interchange and a Names Server. These five services are configured to respond to queries from an SNMP-based network management system.
SNMP.VISIBLESERVICES=(svc-name-x, svc-name-y, svc-name-z...)
This parameter specifies a list of SNMP-managed services. For each database or Oracle network service for which SNMP support is enabled, the name of that service must in the SNMP.VISIBLESERVICES list. The other SNMP.ORA parameters refer to these service names. | |
You must specify service names for database names in the SNMP.VISIBLESERVICES list, for example, HR or SALES. The service name can be an alias to a SQL*Net V1 connect string or the SQL*Net version 2 service name. | |
Each service listed in the SNMP.VISIBLESERVICES line must have an index entry of an integer 1 or greater. |
The integer is used as the value of applIndex, which indexes the applTable of the Network Services MIB, and almost all of the tables in the RDBMS MIB and private MIB. |
SNMP.SID.SERVICE_NAME=SID
This parameter specifies the ORACLE_SID associated with the database. ORACLE_SID is used by the database subagent as the value of applName for this database. | |
The subagent uses the SID in the following ways: | |
· Returns the SID as rdbmsSrvName
· Assumes that services with SIDs are databases
· Assumes that services without SIDs are other types of services
Note: If you do not include a SID for a database, the Subagent assumes that it is a non-database service, and will not connect to it or register any MIB variables for it.
SNMP.CONNECT.SERVICE_NAME=username
This parameter overrides the default username created for the database Subagent. |
SNMP.CONNECT.SERVICE_NAME.PASSWORD=password
This parameter overrides the default username created for the database Subagent. |
Note: This parameter is optional; however, a name and phone number are recommended. Network Manager automatically creates the quotation marks (") around the value for this parameter.
This parameter can be used for any SNMP-managed service and answers queries for the following: | |
rdbmsDbContact | |
rdbmsSrvContact | |
oraNamesTnsContact | |
oraInterchgContactInfo | |
oraListnerContact | |
If this parameter is not used for SNMP service, then either noSuchName is returned for SNMPv1 or noSuchIndex for SNMPv2. | |
DBSNMP.POLLTIME=integer
The integer signifies the interval (in seconds) to be used as a polling interval for the status of each SNMP-managed database. Default is 30 seconds. | |
The Subagent tries every 30 seconds to connect to SNMP-managed databases that are down. | |
This parameter indicates the level of detail the trace facility records for database subagent events. Choices are OFF, USER, or ADMIN. Default is OFF. Selecting USER provides a limited level of tracing; ADMIN provides a more detailed trace. |
This parameter sets the directory where the trace file is placed. Default is operating system specific. On UNIX, for example, it is $ORACLE_HOME/network/trace. |
This parameter establishes the name of the file to which trace information is written. Default is DBSNMP.TRC on most platforms. |
If the value is set to ON, a process identifier is appended to the name of each trace file generated so that several can coexist. The default is OFF. |
This parameter indicates the directory in which to find the log file that is automatically generated for SNMP events. Default is operating system specific. On UNIX, for example, it is $ORACLE_HOME/network/log. |
This parameter sets the name of the log file for Oracle SNMP support. Default is DBSNMP.LOG on most platforms. |