How to Verify the Operation of the MaxDB Fault Monitor

Perform this procedure on each node where MaxDB can run.

1. Log in as superuser to a node or zone that can master the MaxDB resource group.

2. Switch the MaxDB resource group to the node or zone that you logged in to in Step 1.

   # clresourcegroup switch -n node sapdb-rg

   node

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

   sapdb-rg

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

3. Abnormally terminate MaxDB.

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

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

      db-name

      Specifies the name of the MaxDB database instance in uppercase

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

      # kill -9 sapdb-kernel-pid

      sapdb-kernel-pid

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

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

   • Restarting the MaxDB resource

   • Failing over the 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 Sun Cluster HA for MaxDB Fault Monitors

   • SUNW.sapdb Extension Properties

5. Terminate MaxDB normally.

   1. Become the OS user who administers the MaxDB database.

      # su - os-sapdb-adm-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. You specify this user when you set the DB_User extension property as explained in How to Register and Configure a MaxDB Resource. 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.

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

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

   • Restarting the MaxDB resource

   • Failing over the 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 Sun Cluster HA for MaxDB Fault Monitors

   • SUNW.sapdb Extension Properties