User's Guide

Table 2-6 Availability of SGeSAP Storage Layout Options for Different Database RDBMS
Cluster Software BundlesSGeSAP Storage
Layout Options
Supported
Platforms
DB Technology
1. Serviceguard or any Serviceguard Storage Management
bundle (for Oracle)
2. SGeSAP
3. Serviceguard HA NFS Toolkit
PA 9000 ItaniumOracle Single-Instance
1. Serviceguard
2. SGeSAP
3. Serviceguard HA NFS Toolkit (opt.)
idle standby
1. Serviceguard Cluster File System (for Oracle)
2. SGeSAP
CFS
1. Serviceguard Cluster File System for RAC
2. SGeSAP
CFSOracle Real Application
Cluster
1. Serviceguard or any Serviceguard Storage Management
bundle
2. SGeSAP
3. Serviceguard HA NFS Toolkit
NFSSAPDB MAXDB
Oracle Single Instance RDBMS
Single Instance Oracle databases can be used with all three 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>. These directories get shared via the database
package
In addition, any SAP Application Server needs access to the Oracle client libraries, including the Oracle
National Language Support files (NLS) shown in Table 2-7 NLS Files Default Location. The default location
to which the client NLS files get installed differs with the SAP kernel release used:
Table 2-7 NLS Files - Default Location
Client NLS LocationKernel Version
$ORACLE_HOME/ocommon/NLS[_<nls_version>]/admin/data<=4.6
/oracle/<rdbms_version>/ocommon/nls/admin/data4.6
/oracle/client/<rdbms_version>/ocommon/nls/admin/data6.x, 7.x
It is important to notice, that there always is a second type of NLS directory, called the "server" NLS directory.
It gets created during database or SAP Central System installations. The location of the server NLS files is
identical for all SAP kernel versions:
$ORACLE_HOME/common/nls/admin/data
The setting of the ORA_NLS[<nls_version>]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.
During SGeSAP installation it is necessary to create local copies of the client NLS files on each host to which
a failover could take place. SAP Central Instances use the server path to NLS files, while Application Server
Instances use the client path.
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 won't work with SGeSAP since switching
the database would leave the application server without NLS file access.
Oracle 9.x releases no longer maintain NLS compatibility with Oracle 8.x. Also, Oracle 9.x patches introduce
incompatibilities with older Oracle 9.x NLS files. The following constraints need to be met:
Database Instance Storage Considerations 27