Managing Serviceguard Extension for SAP, December 2007

Planning the Storage Layout
Database Instance Storage Considerations
Chapter 274
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 RDBMS 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 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 or higher, 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 existent when using MAXDB or liveCache 7.5,
needs to be local on each node together with entries in /etc/passwd
and /etc/group.