Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for MaxDB Guide Oracle Solaris Cluster |
1. Installing and Configuring HA for MaxDB
Overview of the Installation and Configuration Process for HA for MaxDB
Planning the HA for MaxDB Installation and Configuration
MaxDB Software Version Requirements
HA for MaxDB Configuration Requirements
SAP xserver Configuration Requirements
Supported Configurations of This Data Service
Device Group for the MaxDB Application
Dependencies of the MaxDB Application on SAP xserver
Administration of SAP xserver by a User Other Than Root
Configuration Planning Questions
Installing and Configuring MaxDB
How to Install and Configure MaxDB
How to Enable MaxDB to Run in a Cluster
Verifying the MaxDB Installation and Configuration
How to Verify MaxDB Installation and Configuration on Each Node
Installing the HA for MaxDB Packages
How to Install the HA for MaxDB Packages
Configuring the HAStoragePlus Resource Type to Work With HA for MaxDB
How to Register and Configure an HAStoragePlus Resource
Registering and Configuring HA for MaxDB
Setting HA for MaxDB Extension Properties
Administering SAP xserver as a User Other Than Root
How to Register and Configure an SAP xserver Resource
How to Register and Configure a MaxDB Resource
Tuning the HA for MaxDB Fault Monitors
Factors That Affect the Interval Between Fault Monitor Probes
Operations by the HA for MaxDB Fault Monitors During a Probe
Operations by the MaxDB Fault Monitor During a Probe
Operations by the SAP xserver Fault Monitor During a Probe
Faults Detected by the HA for MaxDB Fault Monitors
Faults Detected by the MaxDB Fault Monitor
Faults Detected by the SAP xserver Fault Monitor
Recovery Actions in Response to Detected Faults
Forcing the MaxDB Database Instance to Be Restarted if the Parent Kernel Process Is Terminated
Verifying the HA for MaxDB Installation and Configuration
How to Verify the Operation of the MaxDB Fault Monitor
How to Verify the Operation of the SAP xserver Fault Monitor
Upgrading the SUNW.sap_xserver Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
After you install, register, and configure HA for MaxDB, verify the HA for MaxDB installation and configuration. Verifying the HA for MaxDB installation and configuration determines if the HA for MaxDB data service makes the MaxDB application highly available.
Verifying the 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.
# 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
# ps -ef | grep kernel | grep db-name
Specifies the name of the MaxDB database instance in uppercase
# kill -9 sapdb-kernel-pid
Specifies the process identities of the MaxDB kernel processes that you determined in Step a
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:
# 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.
# 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.
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.
# ps -ef | grep vserver
# kill -9 xserver-pid
Specifies the process identities of the SAP xserver processes that you determined in Step a
# 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.
# x_server stop