Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Application Configuration
Chapter 2 83
Revisit the hosts of OR930. On each host the following directory should
exist or a symbolic link was created after installation:
/oracle/client/<rdbms_version>/ocommon/nls/admin/data
or
/oracle/client/<rdbms_version>/ocommon/nls/admin/data->/
oracle/<SID>/<rdbms_version>/ocommon/nls/admin/data
<rdbms_version> needs to match the version of the ORACLE client that
was used by SAP during linking the SAP kernel. As <sid>adm you can
find the version by entering.
disp+work -v
If the linked ORACLE version of the SAP system is compatible with the
ORACLE database server used remove the symbolic link (or directory)
and recreate the directory populating it with the nls files of the server
nls files:
cd /oracle/client/<rdbms_version>/ocommon/nls/admin
rm (-rf) data # depends on if it is a
# symbolic link or directory
mkdir data
cp /oracle/<SID>/<rdbms_version>/ocommon/nls/admin/data/*
OR950 Oracle Database Step:
The directory
/oracle/client/<rdbms_version>/ocommon/nls/admin/data needs
to be referenced by the $ORA_NLS33 environment variable of <sid>adm
on all failover hosts. For Central Instance hosts, chance is very high that
this is not the default value.
Setting of $ORA_NLS33 needs to be checked in
/home/<sid>adm/.dbenv_<hostname>.[c]sh on all ci or dbci cluster
nodes. The directory exists locally on all hosts to which a failover of a
DBCI or CI package may occur. Set
ORA_NLS33=/oracle/client/<rdbms_version>/ocommon/nls/admin/d
ata in these files.