1. Installing and Configuring HA for MaxDB
Overview of the Installation and Configuration Process for HA for MaxDB
Planning the HA for MaxDB Installation and Configuration
MaxDB Software Version Requirements
HA for MaxDB Configuration Requirements
SAP xserver Configuration Requirements
Supported Configurations of This Data Service
Device Group for the MaxDB Application
Dependencies of the MaxDB Application on SAP xserver
Administration of SAP xserver by a User Other Than Root
Configuration Planning Questions
Installing and Configuring MaxDB
How to Install and Configure MaxDB
How to Enable MaxDB to Run in a Cluster
Verifying the MaxDB Installation and Configuration
How to Verify MaxDB Installation and Configuration on Each Node
Installing the HA for MaxDB Packages
How to Install the HA for MaxDB Packages
Registering and Configuring HA for MaxDB
Setting HA for 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 MaxDB Resource
Tuning the HA for MaxDB Fault Monitors
Factors That Affect the Interval Between Fault Monitor Probes
Operations by the HA for MaxDB Fault Monitors During a Probe
Operations by the MaxDB Fault Monitor During a Probe
Operations by the SAP xserver Fault Monitor During a Probe
Faults Detected by the HA for MaxDB Fault Monitors
Faults Detected by the MaxDB Fault Monitor
Faults Detected by the SAP xserver Fault Monitor
Recovery Actions in Response to Detected Faults
Forcing the MaxDB Database Instance to Be Restarted if the Parent Kernel Process Is Terminated
Verifying the HA for MaxDB Installation and Configuration
How to Verify the Operation of the MaxDB Fault Monitor
How to Verify the Operation of the SAP xserver Fault Monitor
Upgrading the SUNW.sap_xserver Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
For maximum availability of the MaxDB database, resources that HA for MaxDB requires must be available before the MaxDB database instance is started. An example of such a resource is the file system where programs and libraries for the MaxDB runtime environment reside. To ensure that these resources are available, configure the HAStoragePlus resource type to work with HA for 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 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 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 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 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.
The resource is created in the enabled state.
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 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