Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

this directory to a backup location. This information is then used to determine the reason of the crash. In HA
scenarios, for liveCache versions lower than 7.6, this directory should move with the package. Therefore,
SAP provided a way to redefine this path for each liveCache/MaxDB individually. Serviceguard Extension
for SAP on Linux expects the work directory to be part of the lc package. The mount point moves from
/sapdb/data/wrkto /sapdb/data/<LCSID>/wrk. This directory should not be mixed up with the
directory /sapdb/data/<LCSID>/db/wrk that might also exist. Core files of the kernel processes are
written into the working directory. These core files have file sizes of several Gigabytes. Sufficient free space
needs to be configured for the shared logical volume to allow core dumps.
NOTE: For liveCache starting with version 7.6 these limitations do not exist any more. The working directory
is utilized by all instances (IndepData/wrk) and can be globally shared.
/var/spool/sql: This directory hosts local runtime data of all locally running liveCache/MaxDB Instances.
Most of the data in this directory becomes meaningless in the context of a different host after failover. The
only critical portion that still has to be accessible after failover is the initialization data in
/var/spool/sql/ini. This directory is almost always very small (< 1MB).
Table 4-2 General File System Layout for liveCache (Option 3)
Device NumberLogical
Volume
Volume groupMount PointPackageStorage Type
/sapdb/<LCSID>lc<LCSID>Shared
Exclusive
/sapdb/<LCSID>/wrk*lc<LCSID>Shared
Exclusive
/sapdb /<LCSID>/datanlc<LCSID>Shared
Exclusive
/sapdb/<LCSID>/saplognlc<LCID>Shared
Exclusive
/export/sapdb/programssapnfsShared NFS
/export/sapdb/datasapnfsShared NFS
/export/var/spool/sql/inisapnfsShared NFS
/etc/opt/sdbLocal
* only valid for liveCache versions lower than 7.6.
MaxDB Storage Considerations
Serviceguard Extension for SAP on Linux supports current MaxDB, liveCache and older SAPDB releases.
The considerations made below will apply similarly to MaxDB, liveCache and SAPDB clusters unless otherwise
noticed.
MaxDB distinguishes an instance dependant path /sapdb/<DBSID> and two instance independent paths,
called IndepData and IndepPrograms. By default all three point to a directory below /sapdb.
The paths can be configured in a configuration file called SAP_DBTech.ini. Depending on the version of
the MaxDB database this file contains different sections and settings.
A sample SAP_DBTech.ini for a host with a MaxDB/SAPDB 7.4 (LC1) and an APO 3.1 using a MaxDB/SAPDB
7.3 database instance (AP1):
/var/spool/sql/ini/SAP_DBTech.ini
[Globals]
IndepData=/sapdb/data
IndepPrograms=/sapdb/programs
[Installations]
/sapdb/LC1/db=7.4.2.3,/sapdb/LC1/db
/sapdb/AP1/db=7.3.0.15,/sapdb/AP1/db
[Databases]
Planning the Volume Manager Setup 109