Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

/oracle/C11/sapdatan
/oracle/C11/origlogA
/oracle/C11/origlogB
/oracle/C11/mirrlogA
/oracle/C11/mirrlogB
One ABAP CI, one ABAP DI and one DB
This configuration scenario consists of one SAP Central Instance (= CI), one SAP Dialog Instance (=DI) and
one Database instance (=DB). So one additional dialog instance (= D01) will be added when compared to
the previous example. The CI again is identified by the following name "DVEBMGS00", the dialog instance
is identified by the name "D01" in the file system path. So to add an SAP dialog instance to an existing
configuration only one new file system is required: /usr/sap/C11/D01.
The mount points to be analyzed in a cluster environment are:
SAP Instance
/usr/sap/tmp/
/usr/sap/trans/
/usr/sap/C11/DVEBMGS00/
/usr/sap/C11/D01/ <--- new
/usr/sap/C11/SYS/exe/run
/sapmnt/C11/
/home/C11/adm
DB Instance
When compared with the previous example the file system layout has not changed for the databases (MAXDB
and Oracle). The file systems are just listed here for completeness.
The file system layout in the case of a MaxDB or liveCache database:
/etc/opt/sdb
/sapdb/C11
/sapdb/data
/sapdb/programs
/var/spool/sql
The file system layout in the case of an Oracle database:
/$ORACLE_HOME
/oracle/client
/oracle/oraInventory
/oracle/stage
/oracle/C11/saparch
/oracle/C11/sapreorg
/oracle/C11/sapdata1
...
//oracle/C11/sapdatan
/oracle/C11/origlogA
/oracle/C11/origlogB
/oracle/C11/mirrlogA
/oracle/C11/mirrlogB
Configuration Scenarios 35