Go to main content

Oracle® Solaris Cluster Data Service for SAP liveCache Guide

Exit Print View

Updated: July 2020
 
 

How to Register and Configure HA for SAP liveCache

Use this procedure to configure HA for SAP liveCache as a failover data service for the liveCache database and SAP xserver as a multiple master data service. This procedure assumes that you installed the data service packages. If you did not install the HA for SAP liveCache packages as part of your initial Oracle Solaris Cluster installation, go to Installing the HA for SAP liveCache Package to install the data service packages. Otherwise, use this procedure to configure the HA for SAP liveCache.


Caution

Caution  -  Do not configure more than one SAP xserver resource on the same cluster because one SAP xserver serves multiple liveCache instances in the cluster. More than one SAP xserver resource that runs on the same cluster causes conflicts between the SAP xserver resources. These conflicts cause all SAP xserver resources to become unavailable. If you attempt to start the SAP xserver twice, you receive an error message that says Address already in use.


  1. Assume a root role on one of the nodes in the cluster that will host the liveCache resource.
  2. Copy the lccluster file to the same location as the lcinit file.
    # cp /opt/SUNWsclc/livecache/bin/lccluster \
    /sapdb/LC-NAME/db/sap
    LC-NAME

    Uppercase name of liveCache database instance

  3. Edit the lccluster file to substitute the value for put-LC_NAME-here.
    1. Open the lccluster file.
      # vi /sapdb/LC-NAME/db/sap/lccluster
    2. Replace put-LC_NAME-here with the liveCache instance name.

      The liveCache instance name is the value you defined in the Livecache_Name extension property.

      LC_NAME="liveCache-instance-name"
  4. Add the HAStoragePlus resource to the liveCache resource group.
    # clresourcetype register SUNW.HAStoragePlus
    # clresource create -g livecache-resource-group \
    -t SUNW.HAStoragePlus -p filesystemmountpoints=mountpoint,… \
    -p globaldevicepaths=livecache-device-group \
    -p affinityon=TRUE livecache-storage-resource

    The resource is created in the enabled state.


    Note -  AffinityOn must be set to TRUE and the local file system must reside on global disk groups to be failover.

    For the procedure on how to set up an HAStoragePlus resource, see Planning and Administering Data Services for Oracle Solaris Cluster 4.4.

  5. Register the resource type for liveCache database.
    # clresourcetype register SUNW.sap_livecache
  6. Register the resource type for SAP xserver.
    # clresourcetype register SUNW.sap_xserver
  7. Create a multiple master resource group for SAP xserver. Configure SAP xserver to run on all the potential nodes that liveCache will run on.

    Note -  Configure SAP xserver so that SAP xserver starts on all nodes that the liveCache resources can fail over to. To implement this configuration, ensure that the node-list parameter of the SAP xserver resource group contains all the nodes listed in the liveCache resource groups' node-list. Also, the value of desired_primaries and maximum_primaries of the SAP xserver resource group must be equal to each other.
    # clresourcegroup create -n node-list \
    -p Maximum_primaries=value \
    -p Desired_primaries=value xserver-resource-group
  8. Add the HAStoragePlus resource to the SAP xserver resource group.
    # clresource create \
    -g xserver-resource-group \
    -t SUNW.HAStoragePlus \
    -p filesystemmountpoints=mountpoints \
    -p affinityon=false xserver-storage-resource

    The resource is created in the enabled state.

    For more information about setting up an HAStoragePlus resource, see Enabling Highly Available Local File Systems in Planning and Administering Data Services for Oracle Solaris Cluster 4.4.

  9. Create an SAP xserver resource in this multiple master resource group.
    # clresource create \
    -g xserver-resource-group \
    -t SUNW.sap_xserver \
    -p resource_dependencies_offline_restart= \
    xserver-storage-resource{LOCAL_NODE xserver-resource

    The resource is created in the enabled state.

    See Setting HA for SAP liveCache Extension Properties for a list of extension properties.

  10. Create the liveCache resource.
    # clresource create -g livecache-resource-group \
    -t SUNW.sap_livecache \
    -p livecache_name=LC-NAME \
    -p resource_dependencies_offline_restart=livecache-storage-resource, \
    xserver-resource livecache-resource

    The resource is created in the enabled state.

  11. Ensure that the liveCache resource group is brought online only on the node where the SAP xserver resource group is online.

    To meet this requirement, create on the liveCache resource group a strong positive affinity for the SAP xserver resource group.

    # clresourcegroup set \
    -p rg_affinities=++xserver-resource-group livecache-resource-group
  12. Enable the liveCache failover resource group.
    # clresourcegroup online -M livecache-resource-group
  13. (Optional) Consider configuring your cluster to prevent the APO application server resource group from being brought online on the same node as the liveCache resource group.

    You might plan to run the APO application server on a node to which the liveCache resource can fail over. In this situation, consider using resource group affinities to shut down the APO application server when the liveCache resource fails over to the node.

    To specify this behavior, create on the APO application server resource group a strong negative affinity for the liveCache resource group.

    # clresourcegroup set \
    -p rg_affinities=--liveCache-resource-group apo-resource-group