Veritas Storage Foundation for Oracle 5.0 Graphical User Interface Guide, HP-UX 11i v3, First Edition, May 2008

■ When system availability is critical, use RAID-5 for read-intensive OLTP
workloads to improve database performance and availability. Use RAID-5 logs
to allow fast volume resynchronization in the event of a system crash.
■ For most decision support system (DSS) workloads, where sequential scans
are common, experiment with different striping strategies and stripe-unit
sizes. Put the most frequently accessed tables or tables that are accessed
together on separate striped volumes to improve the bandwidth of data transfer.
See “Tuning for Performance” in the Veritas Storage Foundation for Oracle
Administrator's Guide.
For more about volumes and volume procedures, see the Veritas Enterprise
Administrator Guide.
For more about volumes and volume procedures, see the Volume Manager Web
GUI Online Help.
File system creation guidelines
Follow these guidelines when creating VxFS file systems:
■ Specify the maximum log size when creating file systems for databases. In a
Solaris environment, also specify the maximum block size.
■ Except for specifying the maximum log size and support for large files as
required, use the VxFS defaults when creating file systems for databases.
■ Never disable the intent logging feature of the file system.
■ For redo logs, create a single file system using a simple (and mirrored, if
necessary) volume. Put the other tablespaces and database files on separate
file systems created on striped, striped and mirrored, or RAID-5 volumes.
■ When using the command line, use the mount points to name the underlying
volumes. For example, if a file system named /db01 is to be created on a
mirrored volume, name the volume db01 and the mirrors db01-01 and db01-02
to relate to the configuration objects. If you are using the vxassist command
or the GUI, this is transparent.
Choose a file system block size that matches or is a multiple of the block size of
your Oracle database (db_block_size).
It is possible to have a file system block size that is smaller than the database
block size because the database block-size limit can be bigger than the file system
block size. It is fine if the file system block size is smaller than the database block
size because VxFS will not perform multiple I/O operations for each database I/O
operation. VxFS is capable of performing I/Os with multiple blocks. For example,
Managing your database
File system creation guidelines
44