Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Service for SAP MaxDB Guide Oracle Solaris Cluster 4.1 |
1. Installing and Configuring HA for SAP MaxDB
Overview of the Installation and Configuration Process for HA for SAP MaxDB
Planning the HA for SAP MaxDB Installation and Configuration
SAP MaxDB Software Version Requirements
HA for SAP MaxDB Configuration Requirements
SAP xserver Configuration Requirements
Supported Configurations of This Data Service
Device Group for the SAP MaxDB Application
Dependencies of the SAP MaxDB Application on SAP xserver
Administration of SAP xserver by a User Other Than Root
Configuration Planning Questions
Installing and Configuring SAP MaxDB
How to Install and Configure SAP MaxDB
How to Enable SAP MaxDB to Run in a Cluster
Verifying the SAP MaxDB Installation and Configuration
How to Verify SAP MaxDB Installation and Configuration on Each Node
Installing the HA for SAP MaxDB Package
How to Install the HA for SAP MaxDB Package
Registering and Configuring HA for SAP MaxDB
Setting HA for SAP MaxDB Extension Properties
Administering SAP xserver as a User Other Than Root
How to Register and Configure an SAP xserver Resource
How to Register and Configure a SAP MaxDB Resource
Tuning the HA for SAP MaxDB Fault Monitors
Factors That Affect the Interval Between Fault Monitor Probes
Operations by the HA for SAP MaxDB Fault Monitors During a Probe
Operations by the SAP MaxDB Fault Monitor During a Probe
Operations by the SAP xserver Fault Monitor During a Probe
Faults Detected by the HA for SAP MaxDB Fault Monitors
Faults Detected by the SAP MaxDB Fault Monitor
Faults Detected by the SAP xserver Fault Monitor
Recovery Actions in Response to Detected Faults
Forcing the SAP MaxDB Database Instance to Be Restarted if the Parent Kernel Process Is Terminated
Verifying the HA for SAP MaxDB Installation and Configuration
How to Verify the Operation of the SAP MaxDB Fault Monitor
How to Verify the Operation of the SAP xserver Fault Monitor
For maximum availability of the SAP MaxDB database, resources that HA for SAP MaxDB requires must be available before the SAP MaxDB database instance is started. An example of such a resource is the file system where programs and libraries for the SAP MaxDB runtime environment reside. To ensure that these resources are available, configure the HAStoragePlus resource type to work with HA for SAP MaxDB.
For information about the relationship between resource groups and disk device groups, see Relationship Between Resource Groups and Device Groups in Oracle Solaris Cluster Data Services Planning and Administration Guide.
Configuring the HAStoragePlus resource type to work with HA for SAP MaxDB involves the following operation:
Registering and configuring an HAStoragePlus resource
Perform this procedure on any one cluster node.
# clresourcetype register SUNW.HAStoragePlus
Create this resource in the SAP MaxDB resource group. This resource must perform an affinity switchover for all global devices that are defined for this resource.
# clresource create -d -g sapdb-rg \ -t SUNW.HAStoragePlus -p filesystemmountpoints=mountpoint-list \ -p globaldevicepaths=sapdb-device-group \ -p affinityon=TRUE hsp-resource
Specifies that a new resource is to be created in a disabled state.
Specifies that the resource is to be added to the SAP MaxDB resource group.
Specifies that the resource is an instance of the SUNW.HAStoragePlus resource type.
Specifies a list of valid mount points for the file system.
Specifies the name of the global device group on which the SAP MaxDB software is installed.
Specifies that this resource performs an affinity switchover for all global devices that are defined for this resource.
Specifies that the resource that you are creating is named hsp-resource.
Example 1-6 Creating an HAStoragePlus Resource
# clresource create -g sapdbrg \ -t SUNW.HAStoragePlus -p filesystemmountpoints=/global/sapdbdata \ -p globaldevicepaths=sapdbdg -p affinityon=TRUE hsprs
This example shows the creation of a SUNW.HAStoragePlus resource that has the following characteristics:
The resource is named hsprs.
The resource is a member of a resource group that is named sapdbrg. The creation of this resource group is shown in Example 1-5.
The resource is an instance of the SUNW.HAStoragePlus resource type. The registration of this resource type is not shown in this example.
The mount point for the file system is /global/sapdbdata.
The SAP MaxDB software is installed on a global device group that is named sapdbdg.
The hsprs resource performs an affinity switchover for all global devices that are defined for this resource.
Next Steps