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 1 7
Known Problems and Workarounds
The following are known problems with the HA Monitors product:
JAGae75287: diskmond reports an error when vgchange is working at the same
time
What is the problem? diskmond might report DOWN status for the resource lv_summary
without encountering any LVM or disk failure. This could occur when the command,
vgchange -a n, is issued at the command-line prompt at the same time when diskmond tries
to obtain the resource status.
What is the workaround? There is a possibility that LVM status is changed while diskmond is
checking the status. This is a limitation of diskmond and it is the expected behavior. The LVM
status can be verified manually by using the LVM commands.
JAGab04570: Delay in changing resource state
What is the problem? When SNMP connectivity to dbsnmp (Oracle SNMP) fails, EMS
correctly reports that there are “no instances” of the /rdbms/server/status resource.
However, the “no instance” error can persist for up to 60 seconds after corrective action has
been taken, restarting Oracle SNMP. This can cause errors in processes that are monitoring
the /rdbms/server/status resource. For example, it can cause premature package failures
when a package resource dependency ( RESOURCE_NAME ) is specified.
What is the workaround? When you set up a monitoring request, avoid polling intervals that
are less than 60 seconds. In package configuration files, this is controlled by the
RESOURCE_POLLING_INTERVAL directive.
When a database is not available, an error message indicates that its
resource instance is not available
• What is the problem? If a database is unavailable or its server is down, you may see this
error message: Resource “/rdbms/...” is not available. The message will pop up in
the EMS graphical user interface window when you try to access the following resources:
server_started, allowed_max_connects, peak_connects, usage (for both server
and database), commits, commits_per_sec, database_used, and
database_allocated.
• What is the workaround? Before you try to monitor these particular resources, be sure the
database is available and its server has been started.