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

Document Information

Preface

1.  Installing and Configuring HA for MaxDB

HA for MaxDB Overview

Overview of the Installation and Configuration Process for HA for MaxDB

Planning the HA for MaxDB Installation and Configuration

Configuration Requirements

MaxDB Software Version Requirements

HA for MaxDB Configuration Requirements

SAP xserver Configuration Requirements

Supported Configurations of This Data Service

Configuration Considerations

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

Configuring the HAStoragePlus Resource Type to Work With HA for MaxDB

How to Register and Configure an HAStoragePlus Resource

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

A.  HA for MaxDB Extension Properties

Index

Verifying the MaxDB Installation and Configuration

Before you install the HA for MaxDB packages, verify that the MaxDB software is correctly installed and configured to run in a cluster. This verification does not verify that the MaxDB application is highly available because the HA for MaxDB data service is not yet installed.

How to Verify MaxDB Installation and Configuration on Each Node

Perform this procedure on each node or zone that can master the MaxDB resource group.

  1. Log in as superuser to a node or zone that can master the MaxDB resource group.
  2. Switch the MaxDB resource group to the node that you logged in to in Step 1.
    # clresourcegroup switch -n node sapdb-rg 
    -n node

    Specifies the node to which the MaxDB resource group is to be switched

    sapdb-rg

    Specifies that the MaxDB resource group sapdb-rg is to be switched to another node

  3. Confirm that the MaxDB database can be started and be stopped.
    1. Become the OS user who administers the MaxDB database.
      # su - os-sapdb-adm-user
      os-sapdb-adm-user

      Specifies the UNIX user identity of the OS user who administers the MaxDB database. This user's home directory contains the .XUSER.62 file that was created during the installation and configuration of MaxDB. For more information, see Installing and Configuring MaxDB. You specify this user when you set the DB_User extension property as explained in How to Register and Configure a MaxDB Resource.

      If you are using MaxDB 7.5 or MaxDB 7.6, the UNIX user identity of the OS user who administers the MaxDB database is sdb.

    2. Start the SAP xserver.
      $ x_server start
    3. Manually start the MaxDB database instance on the node that you logged in to in Step 1.
      $ dbmcli -U sapdb-adm-key db_online
      -U sapdb-adm-key

      Specifies that the dbmcli command is run with the user key of the database user who administers the MaxDB instance. This user key is created during the installation and configuration of MaxDB. For more information, see Installing and Configuring MaxDB. You specify this user key when you set the User_Key extension property as explained in How to Register and Configure a MaxDB Resource.

    4. Confirm that the MaxDB database instance is started.
    5. Manually stop the MaxDB database instance.
      $ dbmcli -U sapdb-adm-key db_offline
      -U sapdb-adm-key

      Specifies that the dbmcli command is run with the user key that you used for starting the database in Step c

    6. Confirm that the MaxDB database instance is stopped.