How to Verify the Operation of the SAP DB Fault Monitor

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

1. Log in as superuser to a node that can master the SAP DB resource group.

2. Switch the SAP DB resource group to the node that you logged in to in Step 1.

   # scswitch -z -g sapdb-rg -h node

   -z

   Specifies that the node that masters a resource group is to be switched

   -g sapdb-rg

   Specifies that the SAP DB resource group is to be switched to another node

   -h node

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

3. Abnormally terminate SAP DB.

   1. Determine the process identities of all kernel processes for the SAP DB database instance that you are running.

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

      db-name

      Specifies the name of the SAP DB database instance in uppercase

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

      # kill -9 sapdb-kernel-pid

      sapdb-kernel-pid

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

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

   • Restarting the SAP DB resource

   • Failing over the SAP DB 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 Defining the Criteria for Persistent Faults and Forcing the SAP DB Database Instance to Be Restarted if the Parent Kernel Process Is Terminated.

5. Terminate SAP DB normally.

   1. Become the OS user who administers the SAP DB database.

      # su - os-sapdb-adm-user

      os-sapdb-adm-user

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

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

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

   • Restarting the SAP DB resource

   • Failing over the SAP DB 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 Defining the Criteria for Persistent Faults and Forcing the SAP DB Database Instance to Be Restarted if the Parent Kernel Process Is Terminated.