Managing HP Serviceguard Extension for SAP for Linux, December 2013

installation. If not, it must be installed according to the instructions in SAP note 1031096. The
sapinst used for instance installation may offer an option to install the hostagent. This step can
be executed within or directly after phase 2. Make sure that both the uid of sapadm and the gid
of sapsys are identical in all the cluster nodes.
5.4.6 Other local file systems and synchronization
There are other directories and files created during SAP installation that reside on local file systems
on the primary node. This must be copied to the secondary node(s).
SAP
Recreate directory structure /usr/sap/SID/SYS on all secondary nodes.
MaxDB files
Copy the local /etc/opt/sdb to all the secondary nodes. This is required only after the first
MaxDB or liveCache installation.
If /var/spool/sql was created by the installation (usually only for older versions), recreate the
directory structure on all the secondary nodes.
SAP’s Oracle instant client files
Depending on the Oracle client version, the SAP Oracle instant client files are installed in either
the /oracle/client/11x_64 or /oracle/client/10x_64 directories. Synchronize these
with the secondary nodes.
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
cluster nodes, where its base packages are 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. Halt 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.
72 Clustering SAP Netweaver using SGeSAP packages