Fault monitoring for the HA for Siebel data service is provided by the following fault monitors:
The Siebel Server Fault Monitor
The Siebel Gateway Fault Monitor
Each fault monitor is contained in a resource whose resource type is shown in the following table.
|
Standard properties and extension properties of these resources control the behavior of the fault monitors. The default values of these properties determine the preset behavior of the fault monitors. The preset behavior should be suitable for most Oracle Solaris Cluster installations. Therefore, you should tune the HA for Siebel Fault Monitors only if you need to modify this preset behavior.
Tuning the HA for Siebel Fault Monitors involves the following tasks:
Setting the interval between fault monitor probes
Setting the timeout for fault monitor probes
Defining the criteria for persistent faults
Specifying the failover behavior of a resource
For more information, see Tuning Fault Monitors for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster 4.3 Data Services Planning and Administration Guide. Information about the HA for Siebel Fault Monitors that you need to perform these tasks is provided in the subsections that follow.
Tune the HA for Siebel Fault Monitors when you register and configure HA for Siebel. For more information, see Registering and Configuring HA for Siebel.
During a probe, the Siebel Server fault monitor tests for the correct operation of the following components:
The Siebel Database
If the Siebel Database fails, the status of the Siebel Server is marked as DEGRADED. When the Siebel Database restarts again, the Siebel Server resource probe tries to verify that the Siebel Server is functioning. If this test fails, the Siebel Server is restarted or failed over to another node.
The Siebel Database might not be available when the Siebel Server resource is started. In this situation, the fault monitor also starts the Siebel Server when the Siebel Database becomes available.
The Siebel Gateway
If the Siebel Gateway fails, the status of the Siebel Server is marked as DEGRADED. When the Siebel Gateway restarts again, the Siebel Server resource probe tries to verify that the Siebel Server is functioning. If this test fails, the Siebel Server is restarted or failed over to another node.
The Siebel Gateway might not be available when the Siebel Server resource is started. In this situation, the fault monitor also starts the Siebel Server when the Siebel Gateway becomes available.
The Siebel Server and all its enabled components
If the Siebel Server fails, it is restarted or failed over. If any Siebel component fails, a partial failure is reported. The fault monitor counts this partial failure as 10% of a complete failure.
The Siebel Gateway Fault Monitor monitors the Siebel Gateway process. If the Siebel Gateway process dies, the fault monitor restarts it, or fails it over to another node.