Registering and Configuring HA for MaxDB

To enable HA for MaxDB to make MaxDB highly available, configure Oracle Solaris Cluster data services as follows:

Configure SAP xserver as a scalable data service.
Configure HA for MaxDB as a failover data service.

Before you perform this procedure, ensure that the HA for MaxDB data service packages are installed.

Caution - One SAP xserver serves multiple MaxDB instances and, if SAP liveCache is used, multiple SAP liveCache instances in the cluster. Therefore, do not configure more than one SAP xserver resource on the same cluster. If more than one SAP xserver resource runs on the same cluster, conflicts between the SAP xserver resources occur. These conflicts cause all SAP xserver resources to become unavailable. If you attempt to start the SAP xserver a second time, the attempt fails. The error message Address already in use is also displayed.

Setting HA for MaxDB Extension Properties

The sections that follow contain instructions for registering and configuring resources. These instructions explain how to set only extension properties that HA for MaxDB requires you to set. For information about all HA for MaxDB extension properties, see Appendix A, HA for MaxDB Extension Properties. You can update some extension properties dynamically. You can update other properties, however, only when you create or disable a resource. The Tunable entry indicates when you can update a property.

To set an extension property of a resource, include the following option to modify the resource:

-p property=value

-p property: Identifies the extension property that you are setting
value: Specifies the value to which you are setting the extension property

You can also use the procedures in Chapter 2, Administering Data Service Resources, in Oracle Solaris Cluster Data Services Planning and Administration Guide to configure resources after the resources are created.

Administering SAP xserver as 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:

You must create that user on all cluster nodes or zones that master SAP xserver.
You must define that user when you register and configure an SAP xserver resource. To define the user who administers SAP xserver, set the Xserver_User extension property when you create an SAP xserver resource. For more information about the Xserver_User extension property, see SUNW.sap_xserver Extension Properties.

How to Register and Configure an SAP xserver Resource

Become superuser on a cluster node.

Register the SUNW.sap_xserver resource type.

# clresourcetype register SUNW.sap_xserver

Create a scalable resource group for the SAP xserver resource.
Configure SAP xserver so that SAP xserver starts on all nodes to which the 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 MaxDB resource group. This resource group is created when the procedure How to Enable MaxDB to Run in a Cluster is performed.
```
# clresourcegroup create -n node-zone-list \
-p Maximum_primaries=nodes-in-sapdb-rg \
-p Desired_primaries=nodes-in-sapdb-rg xserver-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 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.

-p Maximum_primaries=nodes-in-sapdb-rg

Specifies the maximum number of nodes on which the SAP xserver resource can start. This number is equal to the number of nodes that are in the node list of the MaxDB resource group. You must specify the same number as the value of the Desired_primaries property.

-p Desired_primaries=nodes-in-sapdb-rg

Specifies the desired number of nodes on which the SAP xserver resource can start. This number is equal to the number of nodes that are in the node list of the MaxDB resource group. You must specify the same number as the value of the Maximum_primaries property.

xserver-rg

Specifies that the resource group that you are creating is named xserver-rg.
Add the HAStoragePlus resource to the SAP xserver resource group.
```
# clresource create -g xserver-rg \
-t SUNW.HAStoragePlus \
-p filesystemmountpoints=mountpoints \
-p affinityon=false xserver-storage-resource
```
-g xserver-rg

Specifies that the resource that you are creating is added to the resource group xserver-rg.

-t SUNW.HAStoragePlus

Specifies that the resource type of the resource you are creating is SUNW.HAStoragePlus.

-p filesystemmountpoints=mountpoint, ...

Specifies the mount points for the resource group you are creating.

-p affinityon=false

Indicates that the SAP xserver resource does not have to be colocated with the device group.

xserver-storage-resource

Specifies that the resource that you are creating is named xserver-storage-resource.

The resource is created in the enabled state.
For more details on how to set up an HAStoragePlus resource, see Enabling Highly Available Local File Systems in Oracle Solaris Cluster Data Services Planning and Administration Guide.
Create an SAP xserver resource in the resource group that you created in Step 3.
```
# clresource create -d -g xserver-rg \
-t SUNW.sap_xserver \
-p resource_dependencies_offline_restart=xserver-storage-resource xserver-resource
```
-g xserver-rg

Specifies that the resource is to be added to the resource group that you created in Step 3

-t SUNW.sap_xserver

Specifies that the resource is an instance of the SUNW.sap_xserver resource type

-p resource_dependencies_offline_restart=xserver-storage-resource

Sets a resource dependency between xserver-storage-resource and the HAStoragePlus resource we created in Step 4.

xserver-resource

Specifies that the resource that you are creating is named xserver-resource.

The resource is created in the enabled state.
Enable the resource group that you created in Step 3.
```
# clresourcegroup online -emM xserver-rg
```
-emM

Enables the resource group and moves it to the MANAGED state.

xserver-rg

Specifies the name of the resource group.

Example 1-7 Configuring a SUNW.sap_xserver Resource

This example shows the sequence of commands that are required to configure an SAP xserver resource. The commands are run on only one cluster node.

The following command creates a scalable resource group to contain an SAP xserver resource for a four-node cluster. The resource group is named xsrvrrg. The xsrvrrg resource group can be brought online on all cluster nodes.
```
# clresourcegroup create \
-p Maximum_primaries=4 \
-p Desired_primaries=4 xsrvrrg
```
The following command adds the HAStoragePlus resource to the SAP xserver resource group. The xserver-storage-resource is called xsstorrs and the mount point, mtp1.
```
# clresource create -d -g xsrvrrg \
-t SUNW.HAStoragePlus \
-p filesystemmountpoints=mtp1 \
-p affinityon=false xsstorrs
```
The resource is created in the enabled state.
The following command creates an SAP xserver resource that is named xsrvrrs in the xsrvrrg resource group. The SAP xserver resource is an instance of the SUNW.sap_xserver resource type. The xserver-storage-resource is xsstorrs. The registration of this resource type is not shown in this example.
```
# clresource create -d -g xsrvrrg -t SUNW.sap_xserver \
-p resource_dependencies_offline_restart=xsstorrs xsrvrrs
```
The resource is created in the enabled state.
The following command moves the xsrvrrg resource group to the MANAGED state and brings the resource group online.
```
# clresourcegroup online -emM xsrvrrg 
```

How to Register and Configure a MaxDB Resource

Register the SUNW.sapdb resource type.
```
# clresourcetype register SUNW.sapdb
```
Create a MaxDB resource in the MaxDB resource group.
Ensure that the MaxDB resource depends on the following resources:
- The HAStoragePlus resource for the global device group on which MaxDB is installed.
- The SAP xserver resource.
When you create this resource, specify the following information about the MaxDB database instance. This information is created when MaxDB is installed and configured as explained in Installing and Configuring MaxDB.
- The name of the MaxDB database.
- The UNIX user identity of the OS user who administers the MaxDB database instance. 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.
- The user key of the database user who administers the MaxDB database instance.
```
# clresource create -d -g sapdb-rg \
-t SUNW.sapdb \
-p DB_Name=db-name \
-p DB_User=os-sapdb-adm-user \
-p User_Key=sapdb-adm-key \
-p resource_dependencies_offline_restart=hsp-resource,xserver-resource sapdb-rs
```
-d

Specifies that the resource that you are creating is not immediately enabled.

-g sapdb-rg

Specifies that the resource is to be added to the MaxDB resource group.

-t SUNW.sapdb

Specifies that the resource is an instance of the SUNW.sapdb resource type.

-p DB_Name=db-name

Specifies the name of the MaxDB database instance in uppercase.

-p DB_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.

-p User_Key=sapdb-adm-key

Specifies the user key of the database user who administers the MaxDB database instance. This user key is created during the installation and configuration of MaxDB. For more information, see Installing and Configuring MaxDB.

-p resource_dependencies_offline_restart=hsp-resource,xserver-resource
Specifies that the MaxDB resource depends on the following resources.
- The HAStoragePlus resource for the global device group on which MaxDB is installed
- The SAP xserver resource
sapdb-rs

Specifies that the resource that you are creating is named sapdb-rs.
The resource is created in the enabled state.
Ensure that the MaxDB resource group is brought online only on a node or zone where the SAP xserver resource group is online.
To meet this requirement, create on the MaxDB resource group a strong positive affinity for the SAP xserver resource group.
```
# clresourcegroup set -p rg_affinities=++xserver-rg sapdb-rg
```
-p rg_affinities=++xserver-rg

Specifies that the MaxDB resource group declares a strong positive affinity for the SAP xserver resource group.

sapdb-rg

Specifies that theMaxDB resource group is to be modified.
Enable the MaxDB resource group.
```
#clresourcegroup online -emM sapdb-rg
```
-emM

Enables the MaxDB resource group and moves it to the MANAGED state.

sapdb-rg

Specifies the name of the MaxDB resource group to be brought online.
(Optional) Consider configuring your cluster to prevent noncritical resource groups from being brought online on the same node or zone as the MaxDB resource group.
You might plan to run lower-priority services on a node to which the MaxDB resource can fail over. In this situation, consider using resource group affinities to shut down the noncritical services when the MaxDB resource fails over to the node.
To specify this behavior, declare on the resource group for each noncritical service a strong negative affinity for the MaxDB resource group.
```
# clresourcegroup set -p rg_affinities=--sapdb-rg noncritical-rg
```
-p

Sets the resource group property to the specified value.

noncritical-rg

Specifies the name of the noncritical resource group.

Example 1-8 Creating a SUNW.sapdb Resource

# clresource create -d -g sapdbrg -t SUNW.sapdb \
-p DB_Name=TST -p DB_User=dbadmin \
-p User_Key=DEFAULT -p resource_dependencies_offline_restart=hsprs,xsrvrrs sapdbrs

The resource is created in the enabled state.

This example shows the creation of a SUNW.sapdb resource that has the following characteristics:

The resource is named sapdbrs.
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.sapdb resource type. The registration of this resource type is not shown in this example.
The MaxDB database instance that is associated with this resource is named TST.
The UNIX user identity of the OS user who administers the MaxDB database is dbadmin.
The user key of the database user who administers the MaxDB database is DEFAULT.
The MaxDB resource depends on the following resources:
- An HAStoragePlus resource that is named hsprs. The creation of the hsprs resource is shown in Example 1-6.
- A SUNW.sap_xserver resource that is named xsrvrrs. The creation of the xsrvrrs resource is shown in Example 1-7.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Service for MaxDB Guide Oracle Solaris Cluster