Managing Serviceguard Extension for SAP Version B.05.10, September 2010

Table 2-9 File System Layout for Oracle RAC in SGeSAP CFS Cluster
Potential Owning
Packages
Access PointMount Point
shared disk and CFS
$ORACLE_HOME/oracle/client
/oracle/<SID>/oraarch
/oracle/<SID>/sapraw
/oracle/<SID>/saparch
/oracle/<SID>/sapbackup
/oracle/<SID>/sapcheck
/oracle/<SID>/sapreorg
/oracle/<SID>/saptrace
/oracle/<SID>/sapdata1...
/oracle/<SID>/sapdatan
/oracle/<SID>/origlogA
/oracle/<SID>/origlogB
/oracle/<SID>/mirrlogA
/oracle/<SID>/mirrlogB
local disk; access via
symbolic link from shared
disk
tnsnames.ora
MAXDB Storage Considerations
SGeSAP supports failover of MAXDB databases as part of SGeSAP NFS cluster option.
Cluster File Systems cannot be used for the MAXDB part of SGeSAP clusters.
The considerations given below for MAXDB will also apply to liveCache and SAPDB clusters,
unless otherwise noted.
MAXDB distinguishes an instance dependant path /sapdb/<DBSID> and two instance
independent paths, called IndepData and IndepPrograms. By default, all three point to a
directory below /sapdb.
The paths can be configured in a configuration file called
/var/spool/sql/ini/SAP_DBTech.ini. Depending on the version of the MAXDB database,
this file contains different sections and settings.
• A sample SAP_DBTech.ini for a host with a SAPDB 7.4 (LC1) and an APO 3.1 using a
SAPDB 7.3 database instance (AP1) from file /var/spool/sql/ini/SAP_DBTech.ini:
[Globals]
IndepData=/sapdb/data
IndepPrograms=/sapdb/programs
[Installations]
/sapdb/LC1/db=7.4.2.3,/sapdb/LC1/db
/sapdb/AP1/db=7.3.0.15,/sapdb/AP1/db
[Databases]
.SAPDBLC=/sapdb/LC1/db
LC1=/sapdb/LC1/db
_SAPDBAP=/sapdb/AP1/db
AP1=/sapdb/AP1/db
[Runtime]
/sapdb/programs/runtime/7240=7.2.4.0,
/sapdb/programs/runtime/7250=7.2.5.0,
/sapdb/programs/runtime/7300=7.3.0.0,
/sapdb/programs/runtime/7301=7.3.1.0,
32 Planning the Storage Layout