High Availability Monitors Version A.03.20 Release Notes

14 Chapter1

Known Problems and Workarounds

The following are known problems with the HA Monitors product or with

Event Monitoring Service:

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,

namely 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 speciﬁed.

What is the workaround? When you set up a monitoring request, avoid

polling intervals that are less than 60 seconds. In package conﬁguration

ﬁles, this is controlled by the

RESOURCE_POLLING_INTERVAL

directive.

JAGab77759: ServiceGuard package service status is

reported incorrectly

What is the problem? /cluster/package/service_status/

<package_name>/<service_name> may be incorrectly reported. When

monitoring the service status of a package running locally and the

ServiceGuard coordinator node is not the same node, service status may

be incorrectly reportedas UNKNOWN or DOWN when it is really UP. cmviewcl

shows the service is UP.

What is the workaround? Conﬁgure package and service status

monitoring on each node in the cluster. Then correlate the data reported

on each node. The coordinator node will report status of UNKNOWN for the

remote service. UNKNOWN state means that the service is up and running

somewhere in the cluster.

JAGad03512: Events could be lost when EMS and HA

Monitors are upgraded

What is the problem? When updating the Event Monitoring Services,