Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for MaxDB Guide Oracle Solaris Cluster |
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
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
To enable HA for MaxDB to make MaxDB highly available, additional installation and configuration operations are required. These operations supplement the standard installation and standard configuration of MaxDB.
During a standard installation, MaxDB is installed with a physical host name. To enable MaxDB to run in a cluster, you must modify MaxDB to use a logical host name.
For information about the standard installation and standard configuration of MaxDB, see the following documentation:
If you are using MaxDB with SAP R/3, see the SAP R/3 documentation for information about how to install and configure SAP R/3 with MaxDB.
If you are using MaxDB independently of SAP R/3, see the MaxDB documentation.
Ensure that you install MaxDB on its own global device group.
Note - 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. You must specify this user in DB_User extension property when you create the MaxDB resource in a later step. Otherwise, the MaxDB fault monitor cannot probe the MaxDB database.
For information about the content of this file, see the MaxDB documentation. For the name of the server on which the database is running, specify the logical host name for the MaxDB resource that you specified in Configuration Planning Questions.
For an example of the content of this file, see Example 1-4.
Use the MaxDB command xuser for this purpose.
# xuser -b user-info-file
Specifies the plain text file from which you are generating the .XUSER.62 file
To ensure that the same owner owns the directory and its contents on all nodes, use the tar(1) command and the rsh(1)
# tar cfB - /usr/spool/sql | rsh destination tar xfB -
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 MaxDB instance.
Copy the /etc/opt/sdb directory and its contents from the node on which you installed MaxDB to all nodes where resources for 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 rsh(1)
# tar cfB - /etc/opt/sdb | rsh destination tar xfB -
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 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 MaxDB instance:
The user key that is used to address this combination of XUSER data is named DEFAULT.
The user name and password of the database user are dbm.
The name of the MaxDB instance is TST.
The logical host name for the MaxDB resource is srvr-1.
No structured query language (SQL) mode is specified.
The default time-out value of the MaxDB instance is used.
The default isolation level of the MaxDB instance is used.
For more information, see the MaxDB documentation.
Use the resource group that you identified when you answered the questions in Configuration Planning Questions.
# clresourcegroup create -n node-zone-list sapdb-rg
Specifies that the resource group that you are creating is named sapdb-rg.
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 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.
# clreslogicalhostname create -g sapdb-rg \ -h sapdb-logical-hostname sapdb-logical-hostname
Specifies that the logical host name's database resource is to be added to the failover resource group that you created in Step 1.
Specifies the host name list. You must use this option either when more than one logical host needs to be associated with the new MaxDB resource or when the logical host does not have the same name as the MaxDB resource itself. MaxDB is the resource for the sapdb-logical-hostname that you specified in Configuration Planning Questions.
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 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.
# clresourcegroup online -emM sapdb-rg
Enables the resource group sapdb-rg created in Step 1 and moves it to the MANAGED state.
Example 1-5 Enabling MaxDB to Run in a Cluster
This example shows the sequence of commands that are required to enable MaxDB to run in a cluster. The commands are run on only one cluster node.
The following command creates a failover resource group to contain the MaxDB application resources and the logical host name for the 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
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.
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 -emM sapdbrg