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

Installing and Configuring SAP MaxDB

To enable HA for SAP MaxDB to make SAP MaxDB highly available, additional installation and configuration operations are required. These operations supplement the standard installation and standard configuration of SAP MaxDB.

During a standard installation, SAP MaxDB is installed with a physical host name. To enable SAP MaxDB to run in a cluster, you must modify SAP MaxDB to use a logical host name.

For information about the standard installation and standard configuration of SAP MaxDB, see the following documentation:

How to Install and Configure SAP MaxDB

  1. On one node of the cluster, install the SAP MaxDB software.

    Ensure that you install SAP MaxDB on its own global device group.

  2. Perform a standard configuration of SAP MaxDB.
  3. Create the .XUSER.62 file in the home directory of the operating system user who administers the SAP MaxDB instance.
    1. Create a plain text file that contains information about the database user who administers the SAP MaxDB database instance.

      For information about the content of this file, see the SAP MaxDB documentation. For the name of the server on which the database is running, specify the logical host name for the SAP MaxDB resource that you specified in Configuration Planning Questions.

      For an example of the content of this file, see Example 1-4.

    2. As SAP MaxDB admin user, generate the .XUSER.62 file from the plain text file that you created in Step a.

      Use the SAP MaxDB command xuser for this purpose.

      # xuser -b user-info-file
      -b user-info-file

      Specifies the plain text file from which you are generating the .XUSER.62 file

  4. Copy the /usr/spool/sql directory and its contents from the node on which you installed SAP MaxDB to all nodes where resources for SAP MaxDB and SAP xserver will run.

    To ensure that the same owner owns the directory and its contents on all nodes, use the tar(1) command and the ssh(1).

    # tar cfB - /usr/spool/sql | ssh destination "cd /;tar xfB -"
    destination

    Specifies the node to which you are copying the /usr/spool/sql directory and its contents

    The following example shows a plain text file that contains information about a database user who administers an SAP MaxDB instance.

  5. Distribute /etc/opt/sdb on all nodes to run SAP MaxDB.

    Copy the /etc/opt/sdb directory and its contents from the node on which you installed SAP MaxDB to all nodes where resources for SAP MaxDB and SAP xserver will run.

    To ensure that the same owner owns the directory and its contents on all nodes, use the tar(1) command and the ssh(1).

    # tar cfB - /etc/opt/sdb | ssh destination "cd /;tar xfB -"
    destination

    Specifies the node to which you are copying the /etc/opt/sdb directory and its contents

Example 1-4 Information About a Database User Who Administers a SAP MaxDB Instance

DEFAULT
dbm
dbm
TST
srvr-1
blank line
blank line
-1
-1
blank line        

This example specifies the following information about a database user who administers an SAP MaxDB instance:

For more information, see the SAP MaxDB documentation.

How to Enable SAP MaxDB to Run in a Cluster

  1. Create a failover resource group to contain the SAP MaxDB application resources and the logical host name for the SAP MaxDB resource.

    Use the resource group that you identified when you answered the questions in Configuration Planning Questions.

    # clresourcegroup create -n node-zone-list sapdb-rg
    sapdb-rg

    Specifies that the resource group that you are creating is named sapdb-rg.

    -n node-zone-list

    Specifies a comma-separated, ordered list of zones that can master this resource group. The format of each entry in the list is node. In this format, node specifies the node name and zone specifies the name of a non-global Oracle Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.

    This list is optional. If you omit this list, the global zone of each cluster node can master the resource group.

  2. Ensure that all network resources that you intend to you use are added to your name service database.
  3. Add a logical host name resource to the failover resource group that you created in Step 1.
    # clreslogicalhostname create -g sapdb-rg \
    -h sapdb-logical-hostname sapdb-logical-hostname
    -g sapdb-rg

    Specifies that the logical host name's database resource is to be added to the failover resource group that you created in Step 1.

    -h

    Specifies the host name list. You must use this option either when more than one logical host needs to be associated with the new SAP MaxDB resource or when the IP alias logical host does not have the same name as the SAP MaxDB resource itself. SAP MaxDB is the resource for the sapdb-logical-hostname that you specified in Configuration Planning Questions.

    sapdb-logical-hostname

    Specifies the logical host name of the server on which the database is running. This host name must be the logical host name for the SAP MaxDB resource that you specified in Configuration Planning Questions.


    Note - If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.


  4. Bring the resource group that you created in Step 1 online in a managed state.
    # clresourcegroup online -M sapdb-rg
    -emM

    Enables the resource group sapdb-rg created in Step 1 and moves it to the MANAGED state.

Example 1-5 Enabling SAP MaxDB to Run in a Cluster

This example shows the sequence of commands that are required to enable SAP MaxDB to run in a cluster. The commands are run on only one cluster node.

  1. The following command creates a failover resource group to contain the SAP MaxDB application resources and the logical host name for the SAP MaxDB resource. The resource group is named sapdbrg. The sapdbrg resource group can be brought online on all cluster nodes or zones.

    # clresourcegroup create sapdbrg
  2. The following command adds a logical host name resource to the sapdbrg resource group. The logical host name of the server on which the database is running is srvr-1. When the sapdbrg resource group is brought online, an attempt is made for each node to discover a network interface on the subnet that the host name list identifies.

    # clreslogicalhostname create -g sapdbrg -h sdrvr-1 -d sapdblr 

    Note - If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.


  3. The following command moves the sapdbrg resource group to the MANAGED state, brings the resource group online, and monitors the resources in the resource group.

    # clresourcegroup online -eM sapdbrg