Information about how to embed SAP MaxDB into a Microsoft Cluster environment (MSCS).
Top Level Navigation
1. SAP MaxDB Version Scope of this Document
2. SAP MaxDB Software for MSCS
3. Integration of SAP MaxDB Database in Microsoft Cluster
4. Life Cycle Management for SAP MaxDB in MSCS
1. SAP MaxDB Version Scope of this Document
This document is valid for SAP MaxDB versions up to 7.8. SAP MaxDB 7.8 introduces the concept of isolated installation which significantly changes the installation process.
SAP MaxDB version 7.8 and SAP MaxDB version 7.9 are NOT in scope of this document.
For information about SAP MaxDB and MSCS for versions 7.8 and 7.9 please use the information in the following SAP notes:
1726396 Integration of SAP MaxDB/liveCache 7.8/7.9 into MSCS
576063 Integration of SAP MaxDB in Microsoft Cluster Server
508979 Upgrade of SAP MaxDB/liveCache w/ Cluster MSCS Var.1
2. SAP MaxDB Software for MSCS
The SAP MaxDB cluster software contains customized modules that replace the standard modules for operation in MSCS. In addition there are special modules for managing communication between MaxDB processes and the MSCS management console.
2.1 System Prerequisites
SAP MaxDB 32-bit server software can only be used on 32-bit Microsoft cluster systems. SAP MaxDB 32-bit cluster integration does not work on 64-bit platforms.
2.2 SAP MaxDB Cluster Software Packages
Every SAP MaxDB installation contains packages required for operation in an MSCS environment. No additional database programs or third-party software are needed.
You don't need to make any special settings to install the SAP MaxDB cluster software. The software is always installed automatically in separate directories.
2.3 Restrictions for Using MaxDB in MSCS
With SAP MaxDB versions below 7.8, it is not possible to operate multiple databases independently of each other in the same MSCS environment. This should ensure that only one SAP MaxDB database is installed for each MS cluster.
3. Integration of SAP MaxDB Database in Microsoft Cluster
3.1 General Methods
At the moment, the following methods can be used to integrate a SAP MaxDB database in Microsoft Cluster:
- With SAP products based on 4.6D_EXT, the database can only be integrated in MSCS manually.
- The SAP installation tool SAPInst is available for SAP products that are basis release 620 or higher. SAP Content Server does not offer any tool support and must therefore be integrated using manual methods.
Manual integration does not depend on the SAP environment and can be performed either before or after the integration of the SAP Application Server.
3.2 Explanation of the Configuration Options for SAP MaxDB MSCS Integration
The following designations are still used in relation to MSCS:
- Cluster Storage Disks - are the disks from the MSCS cluster storage device (Source: http://technet.microsoft.com/en-us/library/cc787744.aspx) that are managed as "physical disks" (an MSCS resource type).
- Local Disks: are the disks (or areas) that are accessible from the cluster node at any time.
3.2.1 Distribution of the MaxDB Software in a System
The MaxDB server software package contains the 2 components: "base software" and "kernel software".
The "base software" is the database independent software and the "kernel software" is the database dependent software. These two software components can be installed on different disks.
3.2.2 Location of MaxDB Registration and MaxDB RunTime Directories
Besides the MaxDB software components, additional MaxDB components are available that contain the software registration, MaxDB runtime objects and MaxDB working directories. This component is called "independent data" and is stored in the MaxDB file system.
The location of this component on a configured system can be found using the command "sdbconfig IndepData".
The component must always be accessible from the active node in the MSCS environment. Therefore "independent data" is installed on a cluster storage disk.
3.2.3 Three Options for MaxDB Distribution in MSCS
Due to the separation of the base software and kernel software components, there are three preferred combinations that can be used (depending on the type of operation):
- Type A, "base software" and "kernel software" are installed on cluster storage disks. This option has the advantage of easy software maintenance. This solution is for MaxDB-only cluster operation. No other MaxDB-dependent components (database clients) are allowed on the same cluster. A failover (cluster switch) moves the client software and core software.
- "Base software" is installed on a cluster storage disk
- "Server software" is installed on a cluster storage disk
- Type B, "base software" is available on all cluster nodes simultaneously. The "base software" must be installed on local disks in all cluster nodes. The "kernel software" is located on a cluster storage disk. The advantage of this option is that the client software is always available. Software maintenance is more complicated than with type A. This software distribution is suitable for a MaxDB cluster operation where the other MaxDB client applications also run in the same cluster.
- "Base software" is installed on local disks in all cluster nodes
- "Server software" is installed on a cluster storage disk
- Type C, "base software" and "kernel software" are available on all cluster nodes simultaneously. The two components are installed on local disks in all cluster nodes. It is vitally important to have the same version of the MaxDB software on all cluster nodes. This configuration offers the same advantages as type B for the client applications. However, software maintenance with this configuration is different.
- "Base software" is installed on local disks in all cluster nodes
- "Server software" is installed on local disks in all cluster nodes
3.3 Preparation Before Integration
The following information is required for integration:
- A virtual host name for the MaxDB cluster group and a virtual IP address: During the preparation phase, this information is not linked to any hardware. The information is used later on for the IP resource of the MaxDB cluster group during the integration phase
- Disks: Before proceeding with the installation, you need to know which cluster storage disks are assigned to the MaxDB (distribution type A, B or C). Different cluster storage disks should be used for MaxDB data volumes and log volumes.
3.4 Integration into the First Cluster Node
When you use Sapinst, the MaxDB software is installed as the first step. The relevant MaxDB executables are replaced by customized MaxDB cluster executables. The MaxDB MSCS Manager and the corresponding libraries are copied to the corresponding Windows directories. The MaxDB instance is then created and initialized. Next the MaxDB cluster group is created using the MaxDB MSCS Manager. Resources (IP, disks) are automatically assigned to this group by Sapinst.
For manual MaxDB Integration in MSCS, the MaxDB software must first be installed and the MaxDB instance must be initialized. One of the 3 distribution methods for MaxDB software (type A, B or C) is used (the method used depends on the system prerequisites).
We also recommend that you install the latest version of the MaxDB database instance before proceeding with the cluster integration. Upgrading an integrated MaxDB instance is more complicated than upgrading a non-integrated MaxDB instance. Before copying the MaxDB cluster software, you have to stop x_server (command: x_server stop) and shut down the database instance.
A manual MaxDB integration in MSCS on a cluster node consists of the following steps:
- Copying the MaxDB MSCS executables
- Copying the MaxDB Kernel Software Customized for MSCS Operation
- Registering MaxDB in the Cluster Manager
The way the integration is performed depends on the selected MaxDB software distribution type. The following section describes in detail the activities involved in manual integration.
3.4.1 Copying the MaxDB MSCS Executables
A MaxDB Windows installation always automatically installs the software required for operation in the MCSC environment. This software can be found under this path: <IndepPrograms>\cluster.
You can determine the value for <IndepPrograms> by using the following command:
sdbconfig IndepPrograms
Application extensions: SAPDBMSC*.dll and SAPDBMSCSMan.exe are copied to the Windows Cluster directory: %WINDOWS%\cluster.
The file serv_clu.exe must also be copied as follows:
copy <IndepPrograms>\Cluster\serv_clu.exe <IndepPrograms>\pgm\serv.exe
3.4.2 Copying the MaxDB Kernel Software Customized for MSCS Operation
The MaxDB applications customized for MSCS operation are located in the following directory:
<Database Kernel Software Root>\cluster.
The value of <Database Kernel Software Root> can be determined from the output of the following command:
sdbregview -l | findstr "Database Kernel"
The following copy commands have to be executed:
copy <Database Kernel Software Root>\Cluster\dbmsrv_clu.exe <Database Kernel Software Root>\pgm\dbmsrv.exe
copy <Database Kernel Software Root>\Cluster\service_clu.exe <Database Kernel Software Root>\pgm\service.exe
copy <Database Kernel Software Root>\Cluster\strt_clu.exe <Database Kernel Software Root>\pgm\strt.exe
copy <Database Kernel Software Root>\Cluster\stop_clu.exe <Database Kernel Software Root>\pgm\stop.exe
3.4.3 Registering SAP MaxDB in the Cluster Manager
The registration process comprises the following steps:
- Creating the MaxDB cluster group using the following command in the cmd window:
%WINDOWS%\Cluster\sapdbmscsman -C
The "SAP DBTech" group appears in the Microsoft Cluster Management Console. - Adding the network resource to the MaxDB cluster group:
set network="external LAN connection"
set ipaddress=<virtual IP address for DB host>
set netmask=<netmask>
%WINDOWS%\Cluster\sapdbmscsman -B "%network%,%ipaddress%,%netmask%,Disk D:"
In this example, Disk D: represents the cluster storage disk where the MaxDB registration is recorded (see chapter 3.1.1 Location of MaxDB Registration and MaxDB RunTime Directories). - Adding the remaining MaxDB resources to the MaxDB cluster group:
Every cluster storage disk where MaxDB log and data volumes are configured.
%WINDOWS%\cluster\sapdbmscsman -m "Disk <Drive Letter>:"
Depending on the distribution of MaxDB software (see 3.2.3 Three Possibilities for MaxDB Distribution in MSCS), the cluster storage disks that contain parts of the MaxDB software must also be entered in the MaxDB cluster group. - Creating a resource for the database instance:
%WINDOWS%\cluster\sapdbmscsman -a <DBID> - The database resource must be registered in the Microsoft Cluster Management Console as a resource that is dependent on all other resources in the MaxDB cluster group (see http://technet.microsoft.com/en-us/library/cc758253.aspx).
3.5 Integration of a SAP MaxDB Instance into the Additional MSCS Node
When you use SAPInst, the MaxDB software is copied from the first node as the first step. The MaxDB MSCS Manager and the corresponding libraries are copied to the corresponding Windows directories. The MaxDB software and the instance are then registered. Integration occurs automatically.
A manual MaxDB integration in MSCS on cluster node B consists of the following steps:
- Copying the MaxDB MSCS executables
- Copying the MaxDB software from the first node to the additional node
- Registering the MaxDB software components and services
- Registering the database instance
The way the integration is performed depends on the selected MaxDB software distribution type. The following section describes in detail the activities involved in manual integration.
3.5.1 Copying the MaxDB MSCS Executables
The system cluster folder in the first node must be made available on the additional node. The MaxDB cluster modules are copied to the path %WINDOWS%\Cluster on the additional node. The relevant application extensions are SAPDBMSC.dll and SAPDBMSCSMan.exe.
3.5.2 Copying the MaxDB Software from the First Node to the Additional Node
If the base and database kernel software components are installed on cluster storage disk (type A, cf. 3.2.3 Three Possibilities for MaxDB Distribution in MSCS), no actions are required for this step.
MaxDB Software Distribution of Type B
For this type of software distribution, you need to create the directory structure <IndepPrograms> on the local disk of the additional node. The drive letter for the disk must be identical to the letter used on the first node. The complete content of the <IndepPrograms> directory on the first node must be copied to the corresponding directory on the additional node.
MaxDB Software Distribution of Type C
The directories <IndepPrograms> and <Database Kernel Software Root> must be created on the additional node. Here the driver letter is the same as the letter used on the first node. The complete contents of these folders must be copied from the first node to the additional node.
3.5.3 Registering the MaxDB Software Components and Services
The MaxDB cluster group is assigned to the additional cluster node using Microsoft Cluster Manager for purposes of further integration. All resources of the group remain inactive. Registration of the software components and services is carried out using the following steps:
- The paths <IndepPrograms>\bin;<IndepPrograms>\pgm are added to the system path variable on the additional node.
- The MaxDB registration values IndepPrograms and IndepData are set:
With MaxDB versions lower than 7.6, the dbmcli tool is used:
dbmcli -s dbm_setpath indepprogpath <IndepPrograms>
dbmcli -s dbm_setpath indepdatapath <IndepData>
With MaxDB version 7.6 or higher, the sdbconfig tool is used:
sdbconfig IndepPrograms=<IndepPrograms>
sdbconfig IndepData=<IndepData>
- Registration of database kernel
dbmcli -R <Database Kernel Software Root> inst_reg
- Registering the ODBC driver
The ODBC driver is required for the function of the Database Analyzer. The driver must be registered on each additional cluster node using the following command:
odbcreg SAP DB -i -p <IndepPrograms>
- Customizing the TCP/IP services
For remote communication, the ports from the first node are written to the Service file %WINDOWS%\system32\drivers\etc\services. The following services have to be copied for the additional node:
sql6 <Port Number>/tcp
sql30 <Port Number>/tcp
- Registering the communication server using the command:
x_server install
3.5.4 Registering the Database Service
- For MaxDB versions 7.6 or lower, use the following steps:
Rename the following files:
<IndepData>\config\<database_name>.upc
<IndepData>\wrk\<database_name>\dbm.upc
Execute the following command:
dbmcli -R <Database Kernel Software Root> db_create <DATABASE_NAME> <dbm_user>,<password>
New copies of the files <database_name>.upc and dbm. upc are created. Delete the two new files as they do not contain all the users. Rename the original files to what they were before. - For MaxDB version 7.6 or higher, use the following command for the DB registration:
dbmcli -R <Database Kernel Software Root> db_reg DB <DB_NAME> <dbm_user>,<passwd>
3.6 Customization for Shared Operation with the SAP Application Server
With manual integration you need to customize the connection data, if the SAP application server is run in the same cluster. The XUSER information must address the virtual DB hose and not the physical database host. XUSER data is maintained on both nodes. The following commands are used to create the data:
xuser -U DEFAULT -d <DBID> -n <db_clusterhost> -u <SAPR3>,<passwd> -i 0 -S SAPR3 -t 0 set
xuser -U c -d <DBID> -n <db_clusterhost> -u control,<passwd> set
xuser -U w -d <DBID> -n <db_clusterhost> -u superdba,<passwd> set
This command sequence must be executed by the OS users <sid>adm and SAPService<SID>.
4. Life Cycle Management for SAP MaxDB in MSCS
4.1 Installation
The installation in the MSCS environment is performed using SAPINST for current SAP products or using R3SETUP for older SAP products. Therefore it is possible to immediately integrate OLTP instances and liveCache into the cluster environment during the installation. At the moment, Content Server can only be manually integrated into the cluster. Special installations of SAP products are available that do not have any tool-based support. These installations are performed manually, for example, using note 1257186.
4.2 Upgrade
The upgrade process for a MaxDB instance is described in the relevant Note:
Software distribution type A: note 912246
Software distribution type B: note 843560
Software distribution type C: note 508979
4.3 Uninstallation
A MaxDB instance in the Microsoft cluster environment must be uninstalled manually. Note 1156746 describes how to uninstall a MaxDB instance and the MaxDB software components in MSCS.