Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Planning a File System Layout for SAP in a Serviceguard/LX Cluster Environment
Conclusion: Mount Points, Access Types and SGeSAP/LX Package
Chapter 2 75
Oracle Database Instance Storage Considerations
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:
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/ocommon/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 Serviceguard Extension for SAP on Linux 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.
Table 2-10 NLS Files - Default Location
Kernel
Version
Client NLS Location
<=4.6
$ORACLE_HOME/ocommon/NLS[_<nls_version>]/admin/
data
4.6
/oracle/<rdbms_version>/ocommon/nls/admin/data
6.x
/oracle/client/<rdbms_version>/ocommon/nls/
admin/data
7.0 /oracle/client/<rdbms_version>/instantclient