Managing Serviceguard Extension for SAP Version B.05.10, December 2012

in separate files Installations.ini, Databases.ini, and Runtimes.ini in the
IndepData path /sapdb/data/config.
NOTE: The[Globals] section is commonly shared between LC1/LC2 and AP1/AP2. This
prevents setups that keep the directories of LC1 and AP1 completely separated.
A sample SAP_DBTech.ini, Installations.ini, Databases.ini, and Runtimes.ini
for a host with a liveCache 7.5 (LC2) and an APO 4.1 using a MaxDB 7.5 (AP2) from
/var/spool/sql/ini/SAP_DBTech.ini:
[Globals]
IndepData=/sapdb/data
IndepPrograms=/sapdb/programs
from /sapdb/data/config/Runtimes.ini:
[Runtime]
/sapdb/programs/runtime/7500=7.5.0.0
From /sapdb/data/config/Installations.ini:
[Installations]
/sapdb/LC2/db=7.5.0.15,/sapdb/LC2/db
/sapdb/AP2/db=7.5.0.21,/sapdb/AP2/db
From /sapdb/data/config/Databases.ini:
[Databases]
.M750015=/sapdb/LC2/db
LC2=/sapdb/LC2/db.
M750021=/sapdb/AP2/db
AP2=/sapdb/AP2/db
• MaxDB 7.8 does not create SAP_DBTech.ini anymore. The [Globals] section is defined
in /etc/opt/sdb. With the concept of “isolated installations” , a DB installation contains
its own set of (version specific) executables (/sapdb/<DBSID>/db/bin), its own data
directory (/sapdb/<DBSID>/data), and a specific client directory
(/sapdb/client/<DBSID>). At runtime, there will be a database specific set of x_server
related processes.
The following directories are of special interest:
• /sapdb/programs— This can be seen as a central directory with all MaxDB executables.
The directory is shared between all MaxDB 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 MaxDB instances on the same host. Furthermore, different SAPDB versions
could get installed on the same host. The files in /sapdb/programs should be the latest
version in any MaxDB on the cluster node. Files in /sapdb/programs are downwards
compatible. For liveCache 7.4 and APO 3.1 using SAPDB 7.3, SAPDB 7.4 version executables
must be installed in /sapdb/programs. It is important to realize, that also any SAPDB based
SAP application server instance will use this path to access the database client files.
• /sapdb/data/config— This directory is also shared between instances, though you can
find lots of files that are Instance specific in here; for example,
/sapdb/data/config/<DBSID>.* According to SAP this path setting is static.
• /sapdb/data/wrk— The working directory of the main MaxDB processes is also a
subdirectory of the IndepData path for non-HA setups. If a SAPDB restarts after a crash, it
copies important files from this directory to a backup location. This information is then used
to determine the reason of the crash. In HA scenarios, for SAPDB/MaxDB lower than version
7.6, this directory should move with the package. Therefore, SAP provided a way to redefine
this path for each SAPBDB/MaxDB individually. SGeSAP expects the work directory to be
part of the database package. The mount point moves from /sapdb/data/wrk to
/sapdb/data/<DBSID>/wrk for the clustered setup. This directory should not be mixed up
with the directory /sapdb/data/<DBSID>/db/wrk that might also exist. Core files of the
40 Planning the Storage Layout