SAP MaxDB Active/Active Considerations

In an Active/Active configuration, each server is actively running one SAP MaxDB instance while acting as a backup for the other server in case of failure. The following scenario provides specific requirements that must be adhered to in sequential order when protecting an SAP MaxDB resource instance in an Active/Active configuration.

*Internal Load Balancer is not supported in Active/Active configurations.

Active/Active Scenario

The SAP MaxDB IndepDataPath, IndepProgPath and DependPath are installed locally on both servers.

• The registry file /etc/opt/sdb must exist on each server in the cluster. This file should not be located on shared storage since it must be accessible from the target server during resource extend operations.

• The database instance data device spaces (data devspaces), log device spaces (log devspaces) and system device spaces (sys devspaces) must reside on a shared disk (either shared file system or shared raw device).

• The database instance run directory (RUNDIRECTORY) must be located on shared storage. The value of RUNDIRECTORY can be modified via the DBMCLI command param_directput. If the value of RUNDIRECTORY is modified after the database is created, the database instance must be stopped and restarted to complete the parameter update.

• The database instance config (<IndepDataPath>/config) directory structure must exist in the same location on all servers in the cluster where the database instance will be protected. In addition, the parameter files for the database instance must be copied from the template (or primary) server to all backup servers in the cluster. The parameter files must be redistributed to all servers in the cluster after any parameter has been updated. The required files are:

config/Databases.ini

config/Installations.ini