Managing Serviceguard Extension for SAP Version B.05.10, September 2010

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 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.
For MaxDB version 7.8 or later, this directory is replaced by /sapdb/<DBSID>/data.
NOTE: For MAXDB RDBMS starting with version 7.6, these limitations do not exist. 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 MAXDB
instances. Most of the data in this directory would become 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 usually very small (<
1 Megabyte). With MAXDB and liveCache 7.5 or higher, the only local files are contained
in /var/spool/sql/ini, other paths are links to local runtime data in IndepData path:
dbspeed -> /sapdb/data/dbspeed
diag -> /sapdb/data/diag
fifo -> /sapdb/data/fifo
ipc -> /sapdb/data/ipc
pid -> /sapdb/data/pid
pipe -> /sapdb/data/pipe
ppid -> /sapdb/data/ppid
The links need to exist on every possible failover node in the MAXDB for the liveCache
instance to run. For MaxDB version 7.5 or later, this /var/spool/sql is created only for
compatibility with older versions. Depending on the versions installed it may not exist
anymore.
• /etc/opt/sdb: Only exists when using MAXDB or liveCache 7.5 or later. Needs to be local
on each node together with entries in /etc/passwd and /etc/group.
• /sapdb/client (MaxDB 7.8): Contains the client files in <DBSID> subdirectories for each
database installation.
Table 2-10 shows the file system layout for SAPDB clusters.
34 Planning the Storage Layout