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

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.
• /var/lib/sql: Certain patch level of MaxDB 7.6 and 7.7 (see SAP Note 1041650) use
this directory for shared memory files. Needs to be local on each node.
Table 12 (page 41) shows the file system layout for SAPDB clusters.
NOTE: In HA scenarios, valid for SAPDB/MaxDB versions up to 7.6, the runtime directory
/sapdb/data/wrk is configured to be located at /sapdb/<DBSID>/wrk to support consolidated
failover environments with several MaxDB instances. The local directory /sapdb/data/wrk is
referred to by the VSERVER processes (vserver, niserver), that means VSERVER core dump
and log files will be located there.
Table 12 File System Layout for SAPDB Clusters
Device Minor
Number
VG NameVG TypePotential Owning
Packages
Access
Point
Mount Point
database specificdb<DBSID>shared disk/sapdb/<DBSID>
dbci<DBSID>/sapdb/<DBSID>/wrk*
jdb<dbsid>/sapdb/<DBSID>/data<nr>
jdbjci<DBSID>/sapdb/<DBSID>/saplog<nr>
/sapdb/<DBSID>/data**
environment
specific
db<DBSID>
dbci<DBSID>
shared disk
and HA
NFS
/export/sapdb/programs
/export/sapdb/data
/export/sapdb/client** jdb<DBSID>
/export/var/spool/sql/ini jdbjci<DBSID>
SAPNFS
Database Instance Storage Considerations 41