Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

The discussion of NLS files has no impact on the treatment of other parts of the ORACLE client files.
The following directories need to exist locally on all hosts where an Application Server might run.
The directories cannot be relocated to different paths. The content needs to be identical to the
content of the corresponding directories that are shared as part of the database SGeSAP package.
The setup for these directories follows the "on top" mount approach, that is, the directories might
become hidden beneath identical copies that are part of the package:
$ORACLE_HOME/rdbms/mesg
$ORACLE_HOME/oracore/zoneinfo
$ORACLE_HOME/network/admin
Table 9 File system layout for NFS-based Oracle clusters
VG TypePotential Owning PackagesAccess PointMount Point
DB instance specificDatabase only or combined
DB plus CI package
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 specificNoneLocal/oracle/client
DB instance specificNoneLocalSome local Oracle client files reside in
/oracle/<SID> as part of the root filesystem
MaxDB/liveCache storage considerations
This section describes the recommended storage considerations for MaxDB and liveCache.
NOTE: SGeSAP/LX does not support hoststandby liveCache(HSS), hence the following description
also applies to a liveCache setup, unless noted otherwise. MaxDB can be substituted by liveCache,
<DBSID> by <LCSID>.
The main difference between MaxDB and liveCache is how it is used by the clients. Therefore,
depending on the situation alternative setups are possible for liveCache. For more information on
only liveCache storage considerations, see “Special liveCache storage considerations” (page 40)
section. A High Availabilily (HA) setup for liveCache must ensure that the liveCache client (usually
the SCM installation) has the client libraries.
• SGeSAP supports failover of MaxDB databases as part of SGeSAP NFS cluster option.
• MaxDB distinguishes an instance dependant path /sapdb/<DBSID> and two instance
independent paths, called IndepDataPath and IndepProgramsPath (IndepData and
IndepProgram in ini-file). By default, all three point to a directory below /sapdb.
• The paths are configured in a file called /etc/opt/sdb. For compatibility with older release
there must be a file called /var/spool/sql/ini/SAP_DBTech.ini.
Depending on the version of the MaxDB database, this file contains different sections and
settings.
• The sections [Installations], [Databases], and [Runtime] are stored in separate
files Installations.ini, Databases.ini, and Runtimes.ini in the IndepData
path /sapdb/data/config.
MaxDB/liveCache storage considerations 37