Managing Serviceguard Extension for SAP Version B.05.10, December 2012

NOTE: The configurations are designed to be compliant to SAP OSS note 830982. The note
describes SAP recommendations for Oracle RAC configurations. A support statement from SAP
regarding RAC clusters on HP-UX can be found as part of SAP OSS note 527843. A current support
statement in note 527843 is required, before any of the described RAC options can be implemented.
The note maintenance is done by SAP and the note content may change at any time without further
notice. Described options may have "Controlled Availability" status at SAP.
Real Application Clusters requires concurrent shared access to Oracle files from all cluster nodes.
This can be achieved by installing the Oracle software on Cluster File Systems provided by HP
Serviceguard Cluster File System for RAC.
There are node-specific files and directories, such as the TNS configuration. These files and
directories are copied to a private file system on each node. The node-specific files and directories
are then removed from the shared disks and symbolic links of the same name are created, and
the targets are the corresponding files in the private file system.
Table 11 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.
• For MaxDB and liveCache Version 7.5 (or higher), the SAP_DBTech.ini file does not contain
sections [Installations], [Databases], and [Runtime]. These sections are stored
Database Instance Storage Considerations 39