Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Understanding Serviceguard Extension for SAP on Integrity Linux
Planning the LVM Layout for Clustered SAP Environments
Chapter 1 25
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:
1. The Oracle RDBMS and database tools rely on an
ORA_NLS[<nls_version>] setting that refers to NLS files that are
compatible to the version of the RDBMS. Oracle 9.x needs NLS files
as delivered with Oracle 9.x.
2. The SAP executables rely on an ORA_NLS[<nls_version>] setting
that refers to NLS files of the same versions as those that were used
during kernel link time by SAP development. This is not necessarily
identical to the installed database release.
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. Special
care has to be taken to not mix the access paths for ORACLE server and
client processes.
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 on which an Application Server might run. The content
needs to be identical to the content of the corresponding directories that
are shared as part of the database SGeSAP/LX IPF package (DB or
DBCI):
$ORACLE_HOME/rdbms/mesg
$ORACLE_HOME/oracore/zoneinfo
$ORACLE_HOME/network/admin
NOTE These files can not be relocated to different paths.
Table 1-3 lists the filesystemlayout for ORACLE Cluster. The setup for
these directories follows the “on top” mount approach, i.e., the directories
might become hidden beneath identical copies that are part of the
db/dbci package.