High Availability Monitors Version A.04.00.01 Release Notes

Patches and Fixes in This Version

Chapter 116

Patches and Fixes in This Version

Required and Recommended Patches

The contents of HA Monitors A.03.20.01 and A.03.40 has been incorporated into A.04.00.01

release.

NOTE Before using the HA Database Monitor, be sure you have applied all patches

recommended by Oracle, particularly for the Oracle Intelligent Agent product

(Oracle SNMP), and speciﬁcally any patches pertaining to master_peer (Oracle

SNMP master agent) and start_peer.

Fixes and Changes

The following defects have been ﬁxed in High Availability Monitors A.04.00.01.

JAGae45457

Problem: In a scenario where there are four sets of mirrored disks (eight disks) and four

Physical Volume Groups (PVG) and when one disk is DOWN, pv_summary reports that the

disk is in PVG_DOWN state, even though the corresponding mirrored disk is up and accessible.

Resolution: EMS algorithm has been modiﬁed. Now, pv_summary reports that the disk is in

PVG_UP state.

JAGae13889

Problem: The EMS disk monitor, diskmond, aborts and dumps core if any of the volume group

entries in the /etc/lvmtab ﬁle, have more than 255 Physical Volume Links/Paths.

Resolution: Now, the disk monitor is modiﬁed to dynamically handle any number of Physical

Volume Paths/Links for each of the volume groups.

JAGad92412

Problem: When monitoring MC/ServiceGuard package services with svcmond, EMS reports

Error for the status of service when the package in which the service resides, changes to the

state UNAVAIL. The status of a service in a cluster is identical to the corresponding package

status. Unlike packages, the service monitor in EMS does not recognize the UNAVAIL status as

valid. Hence the UNAVAIL status for services is considered invalid and the resource status is

reported as Error.