Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Siebel Guide SPARC Platform Edition |
Installing and Configuring Oracle Solaris Cluster HA for Siebel
Oracle Solaris Cluster HA for Siebel Overview
Installing and Configuring Oracle Solaris Cluster HA for Siebel
Planning the Oracle Solaris Cluster HA for Siebel Installation and Configuration
Standard Data Service Configurations
Configuration Planning Questions
Installing and Configuring the Siebel Application
How to Install the Siebel Gateway on the Global File System
How to Install the Siebel Gateway on Local Disks of Physical Hosts
Installing the Siebel Server and Siebel Database
How to Install the Siebel Server and Siebel Database on the Global File System
How to Install the Siebel Server and Siebel Database on Local Disks of Physical Hosts
Verifying the Siebel Installation and Configuration
How to Verify the Siebel Installation and Configuration
Installing the Oracle Solaris Cluster HA for Siebel Packages
How to Install the Oracle Solaris Cluster HA for Siebel Packages
Registering and Configuring Oracle Solaris Cluster HA for Siebel
Setting Oracle Solaris Cluster HA for Siebel Extension Properties
How to Register and Configure Oracle Solaris Cluster HA for Siebel as a Failover Data Service
How to Register and Configure the Siebel Server
Verifying the Oracle Solaris Cluster HA for Siebel Installation and Configuration
How to Verify the Oracle Solaris Cluster HA for Siebel Installation and Configuration
Maintaining Oracle Solaris Cluster HA for Siebel
Tuning the Oracle Solaris Cluster HA for Siebel Fault Monitors
A. Oracle Solaris Cluster HA for Siebel Extension Properties
Fault monitoring for the Oracle Solaris Cluster 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.
Table 3 Resource Types for Oracle Solaris Cluster HA for Siebel Fault Monitors
|
System 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 Oracle Solaris Cluster HA for Siebel fault monitors only if you need to modify this preset behavior.
Tuning the Oracle Solaris Cluster 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 Data Services Planning and Administration Guide. Information about theOracle Solaris Cluster HA for Siebel fault monitors that you need to perform these tasks is provided in the subsections that follow.
Tune the Oracle Solaris Cluster HA for Siebel fault monitors when you register and configure Oracle Solaris Cluster HA for Siebel. For more information, see Registering and Configuring Oracle Solaris Cluster 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.
Note - The fault monitor of the Siebel server can detect component failures only in English language installations of Siebel.
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.