Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Linux Configuration
Chapter 3130
cd /import
mkdir trans
mkdir <SID>
mkdir programs
mkdir data
mkdir ini
Be sure to change the ownership of the directories according to your
needs. Normally all SAP directories belong to <sidadm>:sapsys,
while database specific file systems belong to the database user, e.g.
ora<dbsid>:dba or sqd<dbsid>:sapsys.
3. Remove the original directories and replace them with a symbolic
links point to the /import/XXX directories:
rmdir /usr/sap/trans
ln -s /import/trans /usr/sap/trans
rmdir /sapmnt/<SID>
ln -s /import/<SID> /sapmnt/<SID>
rmdir /sapdb/programs
ln -s /import/ programs /sapdb/programs
rmdir /sapdb/data
ln -s /import/data /sapdb/data
rmdir /var/spool/sql/ini
ln -s /import/ini /var/spool/sql/ini
4. Create an entry in the automounter map /etc/auto.import that
maps the client /import directories to the server <nfsvip>:/export
directories. The variable <nfsvip> is the virtual IP address for the
NFS server. Example file entries:
trans -fstype=nfs,rw,udp,nosymlink /
<nfsvip>:/export/usr/sap/trans
<SID> -fstype=nfs,rw,udp,nosymlink /
<nfsvip>:/export/sapmnt/<SID>
programs -fstype=nfs,rw,udp,nosymlink /
<nfsvip>:/export/sapdb/programs
data -fstype=nfs,rw,udp,nosymlink /
<nfsvip>:/export/usr/sapdb/data
ini -fstype=nfs,rw,udp,nosymlink /
<nfsvip>:/export/var/spool/sql/ini