HP Serviceguard Extension for SAP (SGeSAP) manual Sapnfs

this directory to a backup location. This information is then used to determine the reason of the crash. In HA scenarios, for SAPDB/MAXDB lower that version 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.

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.

Table 2-10 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 though is still referred to by the VSERVER processes (vserver, niserver), which means VSERVER core dump and log files will be located there.

Table 2-10 File System Layout for SAPDB Clusters

Mount Point	Access Point	Potential Owning	VG Type	VG Name Device Minor
		Packages		Number
/sapdb/<DBSID>	shared disk	db<DBSID>	database specific
/sapdb/<DBSID>/wrk*		dbci<DBSID>
/sapdb/<DBSID>/data<nr>		jdb<dbsid>
/sapdb/<dbsid>/saplog<nr>		jdbjci<DBSID>
/export/sapdb/programs	shared disk	db<DBSID>	environment
/export/sapdb/data	and HA NFS	dbci<DBSID>	specific
/export/var/spool/sql/ini		jdb<DBSID>
		jdbjci<DBSID>
		SAPNFS
/etc/opt/sdb	local	none
* only valid for SAPDB/MAXDB versions lower than 7.6

Database Instance Storage Considerations 31