Managing HP Serviceguard Extension for SAP for Linux, December 2013

Table 21 Groupfile file groups
RemarkGroups
Primary group for all SAP SID users and DB userssapsys
SAP installer group, secondary for SAP SID and DB userssapinst
MaxDB file ownersdba
Oracle database operators (limited privileges)oper
Oracle database administratorsdba
IBM DB2 authorization groupsdb2<dbsid>admdb2<dbsid>mntdb2<dbsid>ctldb2<dbsid>mon
NOTE: For more information of the terms local, shared exclusive, and shared nfs file
systems used in this section, see chapter 4 “SAP Netweaver cluster storage layout planning” (page
37).
Along with synchronizing user and group information, the HOME directories of the administrators
must be created on the local file system (unless this directory does not reside on a local disk
as in the case for some DB users) on each secondary node.
This duplication of the user’s HOME to secondary nodes is done by running the tar command
on the HOME directory on the primary and unpacking that archive on the secondary.
Use the tar p flag to preserve permissions, user, and group ids.
Some SAP login scripts in the <sid> adm and database admin HOME directories contain versions
for execution on the local node. For example, they contain hostnames in the filename. These login
scripts also have versions for bash (.sh), and csh (.csh). Some files that are often found
are .sapenv, .dbenv, .lcenv, .sapsrc, and .dbsrc (it is not necessary that all of them
exist).
As these files are copied from the primary’s home directories, they will have the primary node
name in the filename. The primary must be replaced with the secondary node name.
For example:
.dbenv.csh on sgxsap51 was duplication from sgxsap50.
On the secondary node, sgsap51 execute:
mv .dbenv_sgxsap50.csh .dbenv_sgxsap51.csh
In the older installations, startsap and stopsap scripts exist with the primary node in the
filename. These must be replaced accordingly.
In the case of the Sybase database administrator, the home directory resides on a shared
exclusive disk. There is no duplication required as the file system is only mounted on the
node running the package. However, the node specific login scripts exist and therefore must be
created for all the secondary nodes. Run the copy command
cp .dbenv_sgxsap50.csh .dbenv_sgxsap51.csh on the primary (instead of the mv
command).
Verification:
Login to each secondary cluster node and su to each user listed in Table 21 (page 70). The
command must not produce errors. If the home directory does not reside on a local file system
but resides on shared file system instead, start the package containing the corresponding volume
group on that node first.
HANA: Provide local secure store file
Within the local copies of the <sid>adm home directory on all nodes, the node-specific secure
store needs to be copied from the file created on only one server during instance installation.
70 Clustering SAP Netweaver using SGeSAP packages