High Availability Monitors Version A.03.01 Release Notes

Chapter 1 9

Known Problems and Workarounds

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

Event Monitoring Service:

opcmsg protocol

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

IT/Operations 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, conﬁgure EMS to send

SNMP traps to ITO for event notiﬁcations from 11.0 managed nodes .

Misleading value for resource instance

/rdbms/server/started

• 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.

• 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.

Wrong value for the resource instance

/rdbms/database/status/

<database_name>

if more than

one database is conﬁgured.

• What is the problem? If you have several databases conﬁgured, the

status of one database is incorrectly reported as the status of all the

other databases.

• What is the workaround? Monitor the corresponding resource

/rdbms/server/status/

<server_name>

instead of

/rdbms/database/status

/<database_name>

. The status of the