Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Planning a File System Layout for SAP in a Serviceguard/LX Cluster Environment
Conclusion: Mount Points, Access Types and SGeSAP/LX Package
Chapter 2 73
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 MaxDB starting with version 7.6 these limitations do not exist any
more. The working directory is used by all instances 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 (< 1Megabyte). With MaxDB and
liveCache 7.5 the only local files are contained in
/var/spool/sql/ini, other paths are just 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 the MaxDB or
liveCache instance is able to run:
• /etc/opt/sdb: Only exists when using MAXDB or liveCache 7.5 or
higher. Needs to be local on each node.