HP Serviceguard Extension for SAP (SGeSAP) manual Maxdb Storage Considerations

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, the targets of which are the corresponding files in the private file system.

Table 2-9 File System Layout for Oracle RAC in SGeSAP CFS Cluster

Mount Point	Access Point	Potential Owning Packages
$ORACLE_HOME/oracle/client	shared disk and CFS

/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

tnsnames.ora	local disk; access via symbolic
	link from shared disk

MAXDB Storage Considerations

SGeSAP supports failover of MAXDB databases as part of SGeSAP NFS cluster option

Cluster File Systems can not 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 noticed.

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):

[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

Database Instance Storage Considerations 29