Managing Serviceguard Extension for SAP Version B.05.10, September 2010

su - sqd<SID>
mkdir -p /sapdb/programs
mkdir -p /sapdb/data
mkdir -p /usr/spool/sql
exit
Ownership and permissions of these directories should be chosen equally to the already existing
directories on the primary host.
MAXDB Database Step: SD235
For releases starting with MAXDB 7.5: Copy file /etc/opt/sdb to the alternate cluster nodes.
This file contains global path names for the MAXDB instance.
MAXDB Database Step: SD236
For releases starting with MAXDB 7.5:
If /var/spool/sql exists, verify that the symbolic links in the directory exist on all cluster
nodes running the database.
Cluster Node Configuration
Repeat the steps in this section for each node of the cluster.
Logon as root.
SGeSAP needs remote login to be enabled on all cluster hosts. The traditional way to achieve
this is via remote shell commands. If security concerns prohibit this, it is also possible to use
secure shell access instead.
Installation Step: IS240
Make sure that the required software packages are installed on all cluster nodes:
Serviceguard Extension for SAP, T2803BA
The swlist command may be utilized to list available software on a cluster node.
If a software component is missing, install the required product depot files using the swinstall
tool.
Installation Step: IS260
You need to allow remote access between cluster hosts.
This can be done by using remote shell remsh(1) or secure shell ssh(1) mechanisms.
If you allow remote access using the remote shell mechanism:
Create an .rhosts file in the home directories of the HP-UX users root and <sid>adm. Allow
login for root as root from all nodes including the node you are logged into. Allow login for
root and <sid>adm as <sid>adm from all nodes including the node you are logged into. Be
careful with this step, many problems result from an incorrect setup of remote access.
Check the setup with remsh commands. If you have to provide a password, the .rhosts does
not work.
Installation Step: IS270
If you allow remote access using the secure shell mechanism:
1. Check with swlist to see if ssh (T1471AA) is already installed on the system:
swlist | grep ssh
If not, it can be obtained from http://www.software.hp.com/ISS_products_list.html.
2. Create a public and private key for the root user:
ssh-keygen -t dsa
Executing this command creates a .ssh directory in the root user's home directory including
the following files:
60 Step-by-Step Cluster Conversion