Faults Detected by the Sun Cluster HA for MaxDB Fault Monitors

Faults that each Sun Cluster HA for MaxDB fault monitor detects are described in the subsections that follow.

Faults Detected by the MaxDB Fault Monitor

The MaxDB fault monitor detects the following faults in MaxDB:

• A status of the MaxDB database instance that is not ONLINE, for example, OFFLINE or ADMIN

• Unexpected termination of the parent kernel process of the MaxDB database instance

The MaxDB fault monitor also detects the unavailability of SAP xserver. This fault monitoring supplements the fault monitoring that the SAP xserver fault monitor provides.

If the MaxDB fault monitor detects that SAP xserver is unavailable twice within the retry interval, the MaxDB fault monitor restarts MaxDB. By restarting MaxDB, the fault monitor ensures that the MaxDB database fails over to another node when SAP xserver is persistently unavailable.

Faults Detected by the SAP xserver Fault Monitor

The SAP xserver fault monitor detects following faults:

• Unavailability of SAP xserver. Unavailability of SAP xserver is also detected by the MaxDB fault monitor.

• Persistent system errors. A persistent system error is a system error that occurs four times within the retry interval. If a persistent system error occurs, the fault monitor restarts SAP xserver.

Recovery Actions in Response to Detected Faults

To minimize the disruption that transient faults in a resource cause, a fault monitor restarts the resource in response to such faults. For persistent faults, more disruptive action than restarting the resource is required:

• For the MaxDB resource, the fault monitor fails over the resource to another node. The MaxDB resource is a failover resource.

• For the SAP xserver resource, the fault monitor takes the resource offline. The SAP xserver is a scalable resource.