Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Linux Configuration
Chapter 256
IS420 Installation Step:
Create a file called /etc/auto.import. This is the indirect automounter
map file. In this file, all cross-mounted directories will now be configured
to be accessed via /import. This action consists of several steps that
belong together. They are combined in one installation step to prevent
that parts of the process are forgotten.
The idea behind the action to be performed here is, that each path below
/export should be automounted from a directory that is directly below
/import.
Refer to the section “Planning the LVM layout for Clustered SAP
Environments” to find out which filesystems and their specified path,
and the SAPDB database specific filesystems
For each directory that has a specified path that shows that it will be
mounted below /export, the following steps have to be done:
1. Make sure there is no filesystem mounted at the specified path
omitting /export. If there is a mountpoint, remove the mounted
filesystem. Example file entries:
umount /usr/sap/trans
umount /sapmnt/<SID>
2. Make sure, that there is no directory at the specified path omitting
/export. If there is a directory, it should be empty by now. It needs to
be removed. Example file entries:
rmdir /usr/sap/trans
rmdir /sapmnt/<SID>
3. Create a new directory directly below /import. It should be possible
to use the last directory of the specified path as new directory name.
Example file entries:
mkdir -p /import/trans
mkdir -p /import/<SID>
Be sure to change the ownership of the directories according to your
needs. Normally all SAP directories belong to <sidadm>:sapsys,
while database specific filesystems belong to the database user, e.g.
ora<dbsid>:dba or sqd<dbsid>:sapsys.
4. Create a link from the specified path omitting /export to the newly
created directory. Example file entries: