Installation guide

Follow the database file system configuration recommendations from the SAP installation

guide. It is recommended to have physically different mount points for the program files and

for saplog and sapdata.

Oracle

Create /oracle/client/10x_64/instantclient locally on every node. See the post-processing

section how to copy the binaries after the installation.

Follow the database file system configuration recommendations from the SAP installation

guide. It is recommended to have different physical mount points for the program files and

for origlog, mirrlog and sapdata.

NOTE: The configuration process gets more complex when multiple database instances of

the same type run within the cluster. The program files must be accessible for every instance.

The mounts from shared storage must be added to the cluster configuration as file system

resources to the failover service.

6.1.3.3 NFS Mounted File Systems

The /sapmnt/<SID> file system should resist on a high available NFS to be available for

additional application server outside the cluster.

The transport directory /usr/sap/trans should also be exported via NFS according to the SAP

landscape.

6.1.3.4 Before Starting the SAP Installation

Before installing SAP NetWeaver, mount all the file necessary systems. Be conscious of the

overmount effect by mounting the hierarchically highest directories first.

6.1.4 Installation with sapinst

When starting the SAP installation tool sapinst, specify the virtual host name.

sapinst SAPINST_USE_HOSTNAME=<virtual hostname>

For each SAP and database instance installed, choose the installation option "High-

Availability System" as described in the SAP installation guide.

6.1.5 lnstallation Post-Processing

6.1.5.1 Users, Groups and Home Directories

Create users and groups on the second node as they were created by the SAP installation on

the first node. Use the same user and group IDs.