High Availability Monitors Version A.03.10 Release Notes

Chapter 1 13

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.

opcmsg protocol

• What is the problem? The opcmsg protocol for communicating with

IT/Operations (ITO) is supported for managed nodes running HP-UX

10.20 but it is not yet available in EMS on HP-UX 11.0.

• What is the workaround? For HP-UX 11.0 do one of the following:

— conﬁgure EMS monitoring requests to send SNMP traps to ITO

for event notiﬁcations from 11.0 managed nodes

— apply patch PHSS_20326

Problems installing software that depends on EMS

• What is the problem? Running swinstall (1M) when installing

products such as HA Monitors, ServiceGuard and other products that

have a dependency on EMS.

It is possible that the product you are installing might include an

older version of EMS than the one that is installed on your system.