Perform this procedure on each node where SAP MaxDB can run.
# clresourcegroup switch -n node sapdb-rg
Specifies the node to which the SAP MaxDB resource group is to be switched
Specifies the name of the SAP MaxDB resource group is to be switched to another node
# ps -ef | grep kernel | grep db-name
Specifies the name of the SAP MaxDB database instance in uppercase
# kill -9 sapdb-kernel-pid
Specifies the process identities of the SAP MaxDB kernel processes that you determined in Step 3.a
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:
# su - 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.
# 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 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.
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: