Managing HP Serviceguard Extension for SAP for Linux, December 2013

For example:
# cat/db2/db2<dbsid>/.rhosts
<vhost> db2<dbsid>
When using ssh for the virtual host configuration, the public key of each physical host in the cluster
must be put into the system's known hosts file. Each of these keys must be prefixed by the virtual
hostname and IP. Otherwise, DB2 triggers an error when the virtual hostname fails over to another
cluster node, and reports different key for the virtual hostname. In addition, password-less ssh
login must be enabled for db2<dbsid> user between cluster nodes.
NOTE: For information about how to setup ssh in a DB2 environment, see the SAP note 1138605
(DB6 - Use ssh as remote shell utility in DPF environment).
HANA: Set up HANA client files on all cluster nodes
Make sure that a copy of the HANA client directory /usr/sap/<SID>/hdbclient is available
on all nodes.
5.4.2 User synchronization
The synchronization of the user environment has the following three sub tasks after completing the
SAP installation:
Synchronize the user and group ids.
Copy home directory to all the secondary nodes.
In the home directory, adap the filenames containing hostnames.
NOTE: The user environment necessary to run the SAP instances and database instances
must be identical on each cluster node.
To be independent of external services to the cluster like DNS or LDAP, local authorization (for
example, /etc/passwd, /etc/shadow, and /etc/group) is recommended for users and
group information. The SAP and database administrators of the various SAP and DB instances
require the entries listed in Table 20 (page 69) table. The database specific user and groups exist
only if SAP is installed with the corresponding database.
Table 20 Password file users
Home directoryPurposeUsername
/home /sapadmSAP system administratorsapadm
/home/<sid>admSAP SID administrator<sid>adm
/home/<dasid>admSAP Diagnostic Agent administrator<dasid>adm
/home/ora<dbsid> or
/oracle/<DBSID> (shared)
Oracle database administratorora<dbsid>
/home/sqd<dbsid>MaxDB database administratorsqd<dbsid>
/home/<lcsid>admliveCache database administrator
1
<lcsid>adm
MaxDB file ownersdb
/sybase/<dbsid> (shared)Sybase database administratorsyb<dbsid>
/db2/db2<dbsid>(shared)DB2 database ownerdb2<dbsid>
/home/sap<dbsid>
/home/sap<dbsid>db
ABAP/Java connect user in a DB2
environment
sap<dbsid>sap<dbsid>db
1
does not follow sqd<dbsid>MaxDB convention.
5.4 Post SAP installation tasks and final node synchronization (Phase 3a) 69