High Availability Monitors Version A.04.20 Release Notes (December 2005)

High Availability Monitors Version A.04.20 Release Notes
Known Problems and Workarounds
Chapter 18
Only Oracle database monitored when both Oracle and Informix
databases installed on same system
• What is the problem? Both Oracle and Informix have their own RDBMS MIB subagents,
and each has its own proprietary method of instrumenting the MIB. The HA Database
Monitor relies on values in the MIB to monitor the databases and database servers. Only
Oracle databases appear even if both subagents are running because of:
— Oracle’s particular implementation
— only one rdbms MIB subagent can receive MIB requests
• What is the workaround? Install each vendor’s database on different systems. If that is not
feasible, and you need to monitor Informix databases, then stop the Oracle SNMP
subagent (dbsnmp) and listener (tnslsnr), and run only the Informix SNMP subagent.
Known Problems and Workarounds for Oracle Installations
Misleading value for resource instance /rdbms/server/started/<server_name>
• What is the problem? The Oracle implementation of the RDBMS public MIB value for the
named resource, rdbmsSrvInfoStartupTime returns a 12-hour clock time, instead of a
24-hour clock time. Therefore, the HA Database Monitor resource instance
/rdbms/server/started/ <server_name> displays only the 12-hour clock time. As a
result, if you are monitoring using the “greater than” notification option, you may not
receive events in some cases.
• What is the workaround? Monitor the resource for changes only. Since the value
represents the time an application server was started, a change to this value is a valid
indication that the server was restarted.
Known Problems and Workarounds for Informix Installations
Resource instance /rdbms/server/uptime/<server_name> is always -l
• What is the problem? The uptime resource should be equal to the number of seconds that
the database server has been in UP state. For Informix, the uptime value is always -1,
which indicates that this value cannot be calculated.
• What is the workaround? Monitor a different resource for changes. For example, monitor
/rdbms/server/started/<server_name> to detect when a server restarts.