User's Guide

If storage layout option 1 is used, create all SAP instance directories below /export as specified in Chapter
2.
For example:
su - <sid>adm
mkdir -p /export/sapmnt/<SID>
mkdir -p /export/usr/sap/trans
exit
MAXDB Database Step: SD290
Create all MAXDB directories below /export as specified in Chapter 2.
For example:
su - sqd<sid>
mkdir -p /export/sapdb/programs
mkdir -p /export/sapdb/data
mkdir -p /export/var/spool/sql/ini
exit
Installation Step: IS300
Each package needs at least one relocatable IP address to be specified.
In case there is a distinction between front-end, server, and LANs. It is likely that at least two addresses are
needed per package. Dedicated heartbeat LANs would require additional addresses. Add all relocatable
IP address information to /etc/hosts. Use Table 3-5 - Relocatable IP Address Information to record the
addresses.
Table 3-5 Relocatable IP Address Information
IP addressname/aliases
Installation Step: IS310
Configure /etc/nsswitch.conf to avoid problems.
If you use DNS:
For example:
hosts: files[NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue]dns
Installation Step: IS330
In some older SAP releases, during installation SAP appends some entries to the standard .profile files
in the user home directories instead of using a new file defined by the SAP System. On HP-UX, by default,
there is the following in the given profiles:
set -u
This confuses the .dbenv*.sh and .sapenv*.sh files of the SAP System. They fail during execution if
the environment is not setup properly. Using SGeSAP the package startup fails trying to bring up the database.
Search the .profile of <sid>adm and remove the set -u, if found.
External Application Server Host Configuration
Repeat the steps in this section for each host that has an external application server installed.
Logon as root.
Installation Step: IS340
If you want to use a secure connection with SSL, refer to IS270 on how to set up secure shell for an application
server hosts.
56 Step-by-Step Cluster Conversion