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

Table 7 Availability of SGeSAP storage layout options for different Database RDBMS
Cluster Software BundlesSGeSAP Storage Layout
Options
DB Technology
SGeSAP NFS clustersOracle Single-Instance 1. Serviceguard
SAP MaxDB
2. SGeSAP
3. Serviceguard NFS toolkit
Sybase ASE
Idle standbyOracle Single Instance 1. Serviceguard
2. SGeSAP
3. Serviceguard NFS toolkit (Optional)
Oracle single instance RDBMS
Single Instance Oracle databases can be used with both SGeSAP storage layout options. The setup
for NFS and NFS Idle Standby Clusters are identical.
Oracle databases in SGeSAP NFS and NFS Idle standby clusters
Oracle server directories reside below /oracle/<DBSID> (for example, /oracle/C11).
These directories get shared via the database package.
ORACLE_HOME usually points to /oracle/<DBSID>/<version>_64 (for example, for Oracle
10.2: /oracle/C11/102_64)
In addition, the SAP Application Servers will need access to the Oracle client libraries, including
the Oracle National Language Support files (NLS) shown in Table 8 (page 36). The default location
where the client NLS files get installed differs with the SAP kernel release used. See the table below:
Table 8 NLS files - default location
Client NLS locationKernel version
/oracle/client/<rdbms_version>/ocommon/nls/admin/data6.x,
/oracle/client/<rdbms_version>/instantclient7.x
For systems using Oracle instant client
(/oracle/client/<major-version>x_64/instantclient) no client side NLS directory
exists.
A second type of NLS directory, called the "server" NLS directory, always exists. This directory is
created during database or SAP Central System installations. The location of the server NLS files
is identical for all supported SAP kernel versions:
$ORACLE_HOME/nls/data
The setting of the ORA_NLS10 variable in the environments of <sid>adm and ora<sid> determines
whether the client or the server path to NLS is used. The variable gets defined in the
dbenv_<hostname>.[c]sh files in the home directories of these users.
However, newer installations don’t define that variable anymore and it is even forbidden to set it
for user <sid>adm (SAP Note 819829)
Sometimes a single host may have an installation of both a Central Instance and an additional
Application Server of the same SAP System. These instances need to share the same environment
settings. SAP recommends using the server path to NLS files for both instances in this case. This
does not work with SGeSAP since switching the database would leave the application server
without NLS file access.
The Oracle database server and SAP server might need different types of NLS files. The server NLS
files are part of the database Serviceguard package. The client NLS files are installed locally on
all hosts. Do not mix the access paths for ORACLE server and client processes.
36 SAP cluster storage layout planning