Understanding the Sun Cluster HA for Oracle E-Business Suite Fault Monitor

This section describes the Sun Cluster HA for Oracle E-Business Suite fault monitor probing algorithm or functionality, states the conditions, and recovery actions associated with unsuccessful probing.

For conceptual information on fault monitors, see the Sun Cluster Concepts Guide.

Resource Properties

The Sun Cluster HA for Oracle E-Business Suite fault monitor uses the same resource properties as resource type SUNW.gds. Refer to the SUNW.gds(5) man page for a complete list of resource properties used.

Probing Algorithm and Functionality

The Sun Cluster HA for Oracle E-Business Suite fault monitor is controlled by the extension properties that control the probing frequency. The default values of these properties determine the preset behavior of the fault monitor. The preset behavior should be suitable for most Sun Cluster installations. Therefore, you should tune the Sun Cluster HA for Oracle E-Business Suite fault monitor only if you need to modify this preset behavior.

• Setting the interval between fault monitor probes (Thorough_probe_interval)

• Setting the timeout for fault monitor probes (Probe_timeout)

• Setting the number of times the fault monitor attempts to restart the resource (Retry_count)

The Sun Cluster HA for Oracle E-Business Suite fault monitor performs a check within an infinite loop. During each cycle the fault monitor will check the relevant component and report either a failure or success.

If the fault monitor is successful it returns to its infinite loop and continues the next cycle of probing and sleeping.

If the fault monitor reports a failure a request is made to the cluster to restart the resource. If the fault monitor reports another failure another request is made to the cluster to restart the resource. This behavior will continue whenever the fault monitor reports a failure.

If successive restarts exceed the Retry_count within the Thorough_probe_interval a request to failover the resource group onto a different node or zone is made.

Concurrent Manager Probe

• Test whether at least one FND (Concurrent Manager) process is running. If this fails, then the probe will restart the Concurrent Manager Server resource.

• Test whether the probe can still connect to the Oracle Database. If this fails, then the probe will restart the Concurrent Manager Server resource.

• Calculate the number of concurrent processes running as a percentage of the maximum number of concurrent processes allowed, and test whether that percentage is less than CON_LIMIT, when the Concurrent Manager Server resource was defined. If the percentage is less than CON_LIMIT, then the probe will restart the Concurrent Manager Server resource.

Forms Server Probe

Test whether the f60srvm process is running. If f60srvm is found, then test whether f60webmx process is running. If f60webmx is not found, then the probe will retest after another iteration of the probe to determine whether f60webmx is still missing, because f60srvm usually restarts f60webmx. If after two successive probes, f60webmx is still missing or f60srvm is not found on any probe, then the probe will restart the Forms Server resource.

Reports Server Probe

Test whether rwmts60 process is running for REP_APPSUSER. If this fails, then the probe will restart the Forms Server resource.