3.7.0 HP StorageWorks HP Scalable NAS File Serving Software provisioning guide for Oracle HP Scalable NAS (AG513-96013, October 2009)

On a local disk we create a mount point /u01/app/oracle owned by the Oracle
user. Then we add a mount in /etc/fstab for /u01/app/oracle exported from
VNFS 192.168.60.71 and /u02 exported from VNFS 192.168.60.79.
The /etc/fstab entries would be:
#ORACLE_HOME
192.168.60.71:/u03/app/oracle /u01/app/oracle nfs <mount options>
# ORACLE DATAFILES
192.168.60.79: /u04 /u02 nfs <mount options>
See NFS mount options, below, for more information about the mount options.
Next, we mount these filesystems:
mount /u01/app/oracle
mount /u02
If the NAS administrator has preset the oracle ownership, you should see these files
as owned by oracle with the proper groups. Otherwise, you will need to set the
ownership as follows:
chown -R oracle:oinstall /u01/app/oracle
chown –R oracle:oinstall /u02
Assuming we want to locate oradata at $ORACLE_BASE/oradata and the datafiles
at /u02/oradata, as user oracle, we create the subdirectory /u02/oradata and
then create a soft link from /u01/app/oracle/oradata to /u02/oradata. We
can also create the subdirectories product/11.1.0/db_1 (as an example) as
subdirectories of /u01/app/oracle.
ln –s /u02/oradata /u01/app/oracle/oradata
mkdir –p /u01/app/oracle/product/11.1/db_1
Selecting a mount point at $ORACLE_BASE (/u01/app/oracle) rather than at
the filesystem base (/u01) is a good idea. In some cases (in particular, RAC installs
from 10g on) Oracle requires that its oraInventory files be located on local disk.
The default is to place the files in the same parent directory as $ORACLE_BASE (e.g.,
under /u01/app). If your mount point is in the same subdirectory, anything else in
that directory, including oraInventory, will be on local storage.
System Administrator: deploying database servers with HP Scalable NAS32