JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for SAP MaxDB Guide     Oracle Solaris Cluster 3.3 3/13
search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring HA for SAP MaxDB

HA for SAP MaxDB Overview

Overview of the Installation and Configuration Process for HA for SAP MaxDB

Planning the HA for SAP MaxDB Installation and Configuration

Configuration Requirements

SAP MaxDB Software Version Requirements

HA for SAP MaxDB Configuration Requirements

SAP xserver Configuration Requirements

Supported Configurations of This Data Service

Configuration Considerations

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 Packages

How to Install the HA for SAP MaxDB Packages

Configuring the HAStoragePlus Resource Type to Work With HA for SAP MaxDB

How to Register and Configure an HAStoragePlus Resource

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

Upgrading the SUNW.sap_xserver Resource Type

Information for Registering the New Resource Type Version

Information for Migrating Existing Instances of the Resource Type

A.  HA for SAP MaxDB Extension Properties

Index

Planning the HA for SAP MaxDB Installation and Configuration

This section contains the information that you need to plan your HA for SAP MaxDB installation and configuration.


Note - HA for SAP MaxDB can be configured to run in a whole root or a sparse root non-global zone, if required.



Note - Before you begin, consult your SAP MaxDB documentation for configuration restrictions and requirements that are not imposed by Oracle Solaris Cluster software. For information about restrictions that the Oracle Solaris Cluster software imposes, see the Oracle Solaris Cluster documentation.


Configuration Requirements

The configuration requirements in this section apply only to HA for SAP MaxDB.


Caution

Caution - If your data service configuration does not conform to these requirements, the data service configuration might not be supported.


For requirements that apply to all data services, see Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide.

SAP MaxDB Software Version Requirements

Use SAP MaxDB versions 7.8.2.26, 7.9.7.10, or compatible versions.

HA for SAP MaxDB Configuration Requirements

Configure HA for SAP MaxDB as a failover data service. You cannot configure HA for SAP MaxDB either as a scalable data service or as a multiple master data service. For more information, see the following sections:

SAP xserver Configuration Requirements

To enable client applications to access HA for SAP MaxDB, you must use SAP xserver. Configure SAP xserver as a multiple master data service. Do not configure SAP xserver as a failover data service.

Configure SAP xserver so that SAP xserver starts on all nodes to which the SAP MaxDB resource can fail over. To implement this configuration, ensure that the node list of the SAP xserver resource group contains all nodes that are in the node list of the SAP MaxDB resource group. For more information, see How to Register and Configure an SAP xserver Resource.

Supported Configurations of This Data Service

The HA for SAP MaxDB data service supports configurations that conform to the requirements in Configuration Requirements.

If you plan to use SAP MaxDB with other highly available SAP MaxDB applications, you must also configure the Oracle Solaris Cluster data services for those applications. For more information, see the following table.

SAP MaxDB Application
Oracle Solaris Cluster Data Service
Associated Document
SAP liveCache
Oracle Solaris Cluster HA for SAP liveCache
SAP Web Application Server
Oracle Solaris Cluster HA for SAP Web Application Server
SAP NetWeaver
Oracle Solaris Cluster HA for SAP NetWeaver

The examples that follow show these supported configurations of HA for SAP MaxDB:


Note - HA for SAP MaxDB might support additional configurations. However, you must contact your Oracle service provider for information about additional configurations.


Example 1-1 Two-Node Configuration

This example shows a two-node configuration in which a client application accesses the SAP MaxDB resource through the SAP xserver resource. The characteristics of this configuration are as follows:

image:Illustration: The preceding context describes the graphic.

Example 1-2 Four-Node Configuration With SAP R/3

This example shows a four-node configuration in which SAP MaxDB is used with SAP R/3. This configuration uses multiple Advanced Planner & Optimizer (APO) application servers. The characteristics of this configuration are as follows:

image:Illustration: The preceding context describes the graphic.

Example 1-3 Four-Node Configuration With SAP R/3 and SAP liveCache

This example shows a four-node configuration in which SAP MaxDB is used with SAP R/3 and SAP liveCache. This configuration uses multiple APO application servers. The characteristics of this configuration are as follows:

image:Illustration: The preceding context describes the graphic.

Configuration Considerations

The configuration considerations in the subsections that follow affect the installation and configuration of HA for SAP MaxDB.

Device Group for the SAP MaxDB Application

Ensure that you create a device group for the SAP MaxDB application as follows:

Dependencies of the SAP MaxDB Application on SAP xserver

Configure SAP MaxDB so that SAP MaxDB starts only on a node where SAP xserver is running. To implement this configuration, configure resources and resource groups as follows:

For more information, see Registering and Configuring HA for SAP MaxDB.

Administration of SAP xserver by a User Other Than Root

You might be required to administer SAP xserver as a user other than root. In this situation, you must create and define that user as follows:

Configuration Planning Questions

Answer the questions in this section to plan the installation and configuration of HA for SAP MaxDB.