High Availability Monitors Version A.03.10 Release Notes

Chapter 1 17

Software Availability in Native Languages

Known Problems and Workarounds for Informix

Installations

Resource instance /rdbms/server/uptime<server_name> is

always -l

• What is the problem? The uptime resource should be equal to the

number of seconds that the database server has been up. For

Informix, the uptime value is always -1, which indicates that this

value cannot be calculated.

• What is the workaround? Monitor a different resource for changes.

For example, monitor /rdbms/server/started/<

server_name

to detect when a server restarts.

Resource instance /rdbms/server/peak_connects/<server_name>

is invalid

• What is the problem? peak_connects represents the greatest number

of simultaneous connections to the database server since the server

started. It currently is not being incremented.

• What is the workaround? Monitor a different resource. For example,

monitor /rdgms/server/connects/<

server_name

> to identify

the current number of simultaneous connections.

Software Availability in Native Languages

The HA Monitors documentation, Using High Availability Monitors, is

available in American English (B5736-90025) and in Japanese

(B5736-90026).

HA Monitors depends on, and includes, the interface provided by Event

Monitoring Service (EMS) (Product Number B7609BA). The manual,

Using Event Monitoring Service is available in American English

(B7612-90015) and in Japanese (B7612-90016).