High Availability Monitors Version A.04.00 Release Notes

High Availability Monitors Version A.04.00 Release Notes for HP-UX 11i v1

Known Problems and Workarounds

Chapter 110

Known Problems and Workarounds

The following are known problems with the HA Monitors product:

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

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.

Only Oracle database monitored when both Oracle and Informix

databases installed on same system

• What is the problem? Both Oracle and Informix have their own RDBMS MIB subagents,

and each has its own proprietary method of instrumenting the MIB. The HA Database

Monitor relies on values in the MIB to monitor the databases and database servers. Only

Oracle databases appear even if both subagents are running because of:

— Oracle’s particular implementation

— only one rdbms MIB subagent can receive MIB requests