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

Table 2-8 File System Layout for NFS-based Oracle Clusters
Device Minor
Number
Volume
Group
Name
VG TypePotential Owning
Packages
Access
Point
Mount Point
db instance
specific
dbci<DBSID>
jdb”<DBSID”
jdbjci<DBSID>
dbcijci<DBSID>
shared
disk
$ORACLE_HOME
/oracle/<SID>/saparch
/oracle/<SID>/sapreorg
/oracle/<SID>/sapdata1
...
/oracle/<SID>/sapdatan
/oracle/<SID>/origlogA
/oracle/<SID>/origlogB
/oracle/<SID>/mirrlogA
/oracle/<SID>/mirrlogB
environment
specific
nonelocal
/oracle/client
db instance
specific
nonelocalsome local Oracle client files reside
in /oracle/<SID> as part of the
root filesystem
Oracle Real Application Clusters
Oracle Real Application Clusters (RAC) is an option to the Single Instance Oracle Database
Enterprise Edition. Oracle RAC is a cluster database with shared cache architecture. The SAP
certified solution is based on HP Serviceguard Cluster File System for RAC.
Handling of a RAC database is not included in SGeSAP itself. RAC databases are treated by
SGeRAC and Oracle tools that integrate with SGeSAP. The configuration of SGeSAP packages
for non-database components is identical to non-RAC environments.
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.
Database Instance Storage Considerations 31