Managing Serviceguard Extension for SAP, December 2007

SAP Supply Chain Management
Planning the Volume Manager Setup
Chapter 4210
1
This can be any standard, standalone NFS package. The SAP global
transport directory should already be configured in a similar package.
This explains why this package is often referred to as “the trans
package” in related literature. A trans package can optionally be
extended to also serve the global liveCache fileshares.
Option 3: Full Flexibility
If multiple SAPDB based components are either planned or already
installed, the setup looks different. All directories that are shared
between SAPDB instances must not be part of the liveCache package.
Otherwise a halted liveCache package would prevent that other SAPDB
instances can be started.
Cluster Layout Constraint:
• There is no hot standby system configured.
The following directories are affected:
/sapdb/programs: This can be seen as a central directory with
liveCache/SAPDB binaries. The directory is shared between all
liveCache/SAPDB Instances that reside on the same host. It is also
possible to share the directory across hosts. But it is not possible to use
different executable directories for two liveCache/SAPDB Instances on
the same host. Furthermore, it is not unusual to install different SAPDB
versions on the same host. This can be seen from the LC1/AP1 example
of the SAP_DBTech.ini file printed below. It is a standard version
combination for SCM3.1.
During normal operation, the liveCache most likely won't share the host
with the APO database. But the failover might allow mutual backup
between the liveCache host and the APO host. This implies that the files
in /sapdb/programs have to be of the highest version that any SAPDB
in the cluster has. Files in /sapdb/programs are downwards compatible.
For the liveCache 7.4 and the APO 3.1 using SAPDB 7.3 this means that
within /sapdb/programs there have to be the 7.4 version executables
installed.
/sapdb/data/config: This directory is also shared between instances,
though you can find lots of files that are Instance specific in here, e.g.
/sapdb/data/config/<LCSID>.* According to SAP this path setting is
static.