After you install, register, and configure Sun Cluster HA for MaxDB, verify the Sun Cluster HA for MaxDB installation and configuration. Verifying the Sun Cluster HA for MaxDB installation and configuration determines if the Sun Cluster HA for MaxDB data service makes the MaxDB application highly available.
Verifying the Sun Cluster HA for MaxDB installation involves verifying the operation of the following fault monitors:
The MaxDB fault monitor
The SAP xserver fault monitor
Perform this procedure on each node where MaxDB can run.
Log in as superuser to a node or zone that can master the MaxDB resource group.
Switch the MaxDB resource group to the node or zone that you logged in to in Step 1.
# clresourcegroup switch -n node sapdb-rg |
Specifies the node to which the MaxDB resource group is to be switched
Specifies the name of the MaxDB resource group is to be switched to another node
Abnormally terminate MaxDB.
Determine the process identities of all kernel processes for the MaxDB database instance that you are running.
# ps -ef | grep kernel | grep db-name |
Specifies the name of the MaxDB database instance in uppercase
Kill all kernel processes for the MaxDB database instance that you are running.
# kill -9 sapdb-kernel-pid |
Specifies the process identities of the MaxDB kernel processes that you determined in Step a
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:
Terminate MaxDB normally.
Become the OS user who administers the MaxDB database.
# su - 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.
Manually stop the MaxDB database instance.
# dbmcli -U sapdb-adm-key db_offline |
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.
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:
Perform this procedure on each node that can master SAP xserver.
Log in to a node or zone that can master SAP xserver.
Abnormally terminate SAP xserver.
Determine the process identities of all SAP xserver processes.
# ps -ef | grep vserver |
Kill all SAP xserver processes.
# kill -9 xserver-pid |
Specifies the process identities of the SAP xserver processes that you determined in Step a
Confirm that the SAP xserver fault monitor restarts the SAP xserver resource.
Terminate SAP xserver normally.
Become the OS user who administers SAP xserver.
# su - os-sapxsrvr-adm-user |
Specifies the UNIX user identity of the OS user who administers SAP xserver. By default, this user is root. You can specify this user by setting the Xserver_User extension property. For more information, see SUNW.sap_xserver Extension Properties.
Manually stop the SAP xserver.
# x_server stop |
Confirm that the SAP xserver fault monitor restarts the SAP xserver resource.