Useful Mounting Options (Client); Rsize And Wsize; Installation Of Oracle Software; Installation Of Oracle On Nas 8000 - HP StorageWorks 8000 - NAS User Manual

desirable in certain situations when the data is easily reproducible and/or connect-time charges are a
limiting factor.

useful mounting options (client)

exec – allows execution of binaries from the mount
intr – applies to hard mounts only. Allows the nfs client to interrupt an nfs request that is waiting.
suid – allows set-user-id bit to function as expected on files in the mounted tree
sync – force all access on mount to be performed synchronously.
vers=# - Specifies whether to use version 2 or version 3 of the nfs protocol. The NAS 8000 supports both
version 2 and version 3. Performance may be slightly improved by using version 3.
nfsvers=# - LINUX. Same as vers above.
rsize=#### – Sets the size of the nfs read buffer to #### bytes. Check the client default. Must be at least
the same as the Oracle Data Block size and is usually a multiple of the data block size. 16384 is a
value that works well for many implementations. (See below)
wsize=#### – Sets the size of the nfs write buffer to #### bytes. Check the client default. Must be at least
the same as the Oracle Data Block size and is usually a multiple of the data block size. 16384 is a
value that works well for many implementations. (See below)

rsize and wsize

These parameters size the nfs read/write "buffers" and can dramatically affect system/database
performance. If the rsize parameter is set to 16384 (16k), all nfs read requests would return 16k bytes.
This can greatly reduce the number of physical reads and nfs packets that must be constructed and sent
when compared to an rsize of say, 512 bytes. It is very important that rsize and wsize be a multiple of the
Oracle db_block_size parameter. If rsize/wsize is less than (or is not a multiple of) the Oracle
db_block_size parameter, nfs will be reading/writing partial Oracle data blocks. This will cause multiple
nfs requests for an Oracle operation and can lead to a loss of data integrity. Please consult with the Oracle
server/IT network administrator for appropriate values. Depending upon the network bandwidth, it may be
beneficial to increase the db_block_size parameter, and this may require a change to these parameters
(rsize/wsize) as well. A general rule of thumb, the faster the network, the larger the block sizes can be.
However, if the buffer size is increased until it is too large, it will increase network collisions and slow the
system down. NOTE: db_block_size must be set before a database is created. Once the database is
created, db_block_size may not be changed without recreating the entire database.

installation of Oracle software

installation of Oracle on NAS 8000

The Oracle ORDBMS (Object Relational DataBase Management System) may be installed to the NAS
8000. That is to say, the NAS 8000 may be used to store the Oracle binaries and support files that are
accessed and executed by the Oracle server. The NAS 8000 does not execute any of the Oracle binaries.
The ability to place one set of Oracle executables on the NAS 8000 and then allow access by several
Oracle servers does not alleviate the customer from securing the appropriate licenses from Oracle.
Additionally, since the NAS 8000 supports a heterogeneous environment, it is possible that several different
Oracle versions/installations could be placed on the NAS 8000. In this scenario, care must be taken to
assure that each Oracle server accesses the appropriate Oracle executables.

setUID bit

If the Oracle executables are stored on the NAS 8000, the UNIX Oracle server system must be configured
as a trusted host. There are some Oracle executable files that use the SetUID bit in their permissions. This
causes the executable to run as the owner of the executable, rather than as the user that invoked the
executable. As a default security feature, when the 'root' user from any Unix system accesses the NAS
8000, the NAS 8000 maps the user 'root' (uid = 0) to the user 'nobody' (uid = 65534). This is a security
feature to protect other users of the NAS 8000. When an Oracle executable that is expected to execute as
'root' (on the Oracle server), is accessed on the NAS 8000, it will be executed as the user 'nobody' unless
the Oracle server is configured as a "host with root access" (also known as a trusted host) via the NAS
8000 management GUI. This can be accomplished in the NAS 8000 GUI by selecting the configuration
tab, then selecting 'UNIX settings' from the left hand tree, then selecting NFS properties. Choose the
actions menu item and edit the NFS properties. In the box 'allow root access' place the system name, or IP
8