Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

For more information about the Oracle Instant Client Installation and Configuration into SAP

environments, see SAP note 819829.

Oracle client installation for MDM

If an MDM configuration is configured as a distributed Oracle configuration, for example, database

and MDM server run in separate packages, then the full Oracle client installation is required.

1. After the installation, update tnsnames.ora with the virtual hostnames as described in

“Check Database Configuration Files”.

2. Synchronize /oracle/client with all the secondary nodes.

3. Set the environment for the mdm<SID> administrator as follows:

export LD_LIBRARY_PATH=/oracle/client/112_64/lib

export ORACLE_HOME=/oracle/client/112_64

4. Synchronize these with the secondary nodes.

Verification:

After synchronization, it is possible to manually start up the SAP instances and database on all the

clusters, where its base packages is configured.

Follow the below procedure to test the manual start and stop of SGeSAP clustering:

1. Stop the SAP instances and or database intended for this package (by using stopsap or

other sap commands like sapcontrol).

2. Stop that package on the local node.

3. Start the package on another cluster node.

4. Start the SAP instances on the new cluster node.

This is the preliminary test for SGeSAP clustering. If the test fails, clustering the SAP instance

later on with SGeSAP also fails.

Completing SGeSAP package creation (Phase 3b)

The three options for creating the final SGeSAP package are as follows:

• Easy deployment with deploysappkgs command.

• Guided configuration using Serviceguard Manager.

• Package creation with the CLI interface using the cmmakepkg and cmapplyconf command.

Creating SGeSAP package with easy deployment

To create the packages with the deploysappkgs command run:

deploysappkgs combi C11

deploysappkgs multi C11

This command attempts to create either a minimal (combi = combine instances) or a maximum

(multi = multiple instances) number of packages. If suitable base packages are already created in

phase 1, it extends those packages with the necessary attributes found for the installed C11

instance.

If necessary, the configuration file for the enqor multi-node package is also created. You must

review the resulting configuration files before applying them. Depending on the attributes changed

or added, cmapplyconf command might fail, and stop running packages.

64 Clustering SAP using SGeSAP packages