HP-UX
Configuration topics for Oracle database on HP-UX with ONTAP.
HP-UX NFS Mount Options
The following table lists the HP-UX NFS mount options for a single instance.
File type | Mount options |
---|---|
ADR Home |
|
Control files |
|
|
|
The following table lists the HP-UX NFS mount options for RAC.
File type | Mount options |
---|---|
ADR Home |
|
Control files |
|
CRS/Voting |
|
Dedicated |
|
Shared |
|
The primary difference between single-instance and RAC mount options is the addition of noac
and forcedirectio
to the mount options. This addition has the effect of disabling host OS caching, which enables all instances in the RAC cluster to have a consistent view of the state of the data. Although using the init.ora
parameter filesystemio_options=setall
has the same effect of disabling host caching, it is still necessary to use noac
and forcedirectio
.
The reason noac
is required for shared ORACLE_HOME
deployments is to facilitate consistency of files such as Oracle password files and spfiles. If each instance in a RAC cluster has a dedicated ORACLE_HOME
, this parameter is not required.
HP-UX VxFS mount options
Use the following mount options for file systems hosting Oracle binaries:
delaylog,nodatainlog
Use the following mount options for file systems containing datafiles, redo logs, archive logs, and control files in which the version of HP-UX does not support concurrent I/O:
nodatainlog,mincache=direct,convosync=direct
When concurrent I/O is supported (VxFS 5.0.1 and later, or with the ServiceGuard Storage Management Suite), use these mount options for file systems containing datafiles, redo logs, archive logs, and control files:
delaylog,cio
The parameter db_file_multiblock_read_count is especially critical in VxFS environments. Oracle recommends that this parameter remain unset in Oracle 10g R1 and later unless specifically directed otherwise. The default with an Oracle 8KB block size is 128. If the value of this parameter is forced to 16 or less, remove the convosync=direct mount option because it can damage sequential I/O performance. This step damages other aspects of performance and should only be taken if the value of db_file_multiblock_read_count must be changed from the default value.
|