Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

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.
• /sapdb/clients (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.
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 are located there.
Table 10 File system layout for SAPDB clusters
VG TypePotential Owning
Packages
Access PointMount Point
DB specificDB only or combined DB
and CI package
Shared disk/sapdb/<DBSID>
/sapdb/<DBSID>/wrk
*
/sapdb/<DBSID>/sapdata<nr>
/sapdb/<DBSID>/saplog<nr>
/sapdb/<DBSID>/data
**
/sapdb/data<DBSID>/data<n>|log<n>
***
Environment specificDB only or combined
DB+CI
Shared disk
and NFS
toolkit
/export/sapdb/programs
/export/sapdb/data
/export/sapdb/clients
**
SAPNFS
/export/var/spool/sql/ini
NoneLocal/etc/opt/sdb
Environment specificNoneLocal/var/lib/sql
*Only valid for versions lower than 7.6.
**Only valid for versions 7.8 or higher.
*** Only valid for older versions.
NOTE: When using tar or cpio to copy or move directories, it must be ensured that the file or
ownership permissions transported are retained, especially for files having the s-bit set:
/sapdb/<SID>/db/pgm/lserver and /sapdb/<SID>/db/pgm/dbmsrv. These files are
important for the vserver process ownership and they have an impact on starting the SAPDB via
<sid>adm.
Database and SAP instances depend on the availability of /sapdb/programs. To minimize
dependencies between otherwise unrelated systems, using a dedicated SAPNFS package is strongly
recommended—especially when the cluster has additional SAP application servers installed, more
than one SAPDB is installed, or the database is configured in a separate DB package. Keeping
local copies is possible, though not recommended because there are no administration tools that
keep track of the consistency between the local copies of these files on all the systems.
Using NFS toolkit filesystems underneath or export Table 10 (page 39) is required when multiple
MaxDB based components (including liveCache) are either planned or already installed. These
MaxDB/liveCache storage considerations 39