Oracle^® Solaris Cluster Data Service for SAP MaxDB Guide

How to Verify the Operation of the SAP MaxDB Fault Monitor

Perform this procedure on each node where SAP MaxDB can run.

1. Assume a root role to a node that can master the SAP MaxDB resource group.
2. Switch the SAP MaxDB resource group to the node that you logged in to in Step 1.

   # clresourcegroup switch -n node sapdb-rg

   node

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

   sapdb-rg

   Specifies the name of the SAP MaxDB resource group is to be switched to another node

3. Abnormally terminate SAP MaxDB.
   1. Determine the process identities of all kernel processes for the SAP MaxDB database instance that you are running.

      # ps -ef | grep kernel | grep db-name

      db-name

      Specifies the name of the SAP MaxDB database instance in uppercase

   2. Kill all kernel processes for the SAP MaxDB database instance that you are running.

      # kill -9 sapdb-kernel-pid

      sapdb-kernel-pid

      Specifies the process identities of the SAP MaxDB kernel processes that you determined in Step a

4. Confirm that the HA for SAP MaxDB fault monitor performs the appropriate operation from the following list:

   • Restarting the SAP MaxDB resource

   • Failing over the SAP MaxDB resource to another node

   The expected behavior of the fault monitor depends on the failure history of the resource and the value of the Failover_enabled extension property. For more information, see the following sections:

   • Tuning the HA for SAP MaxDB Fault Monitors

   • SUNW.sapdb Extension Properties

5. Terminate SAP MaxDB normally.
   1. Become the OS user who administers the SAP MaxDB database.

      # su - os-sapdb-adm-user

      os-sapdb-adm-user

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

   2. Manually stop the SAP 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 of the database user who administers the SAP MaxDB database. This user key is created during the installation and configuration of SAP MaxDB. For more information, see Installing and Configuring SAP MaxDB. You specify this user key when you set the User_Key extension property as explained in How to Register and Configure a SAP MaxDB Resource.

6. Confirm that the HA for SAP MaxDB fault monitor performs the appropriate operation from the following list:

   • Restarting the SAP MaxDB resource

   • Failing over the SAP MaxDB resource to another node

   The expected behavior of the fault monitor depends on the failure history of the resource and the value of the Failover_enabled extension property. For more information, see the following sections:

   • Tuning the HA for SAP MaxDB Fault Monitors

   • SUNW.sapdb Extension Properties