HP XP Array Manager Software - Manual (Page 15)

Note: The Oracle database needs to be constructed on raw devices (for example, no file system).
Also, you need to set the DB_BLOCK_CHECKSUM parameter to TRUE.
Note: Oracle database functionality of check data is slightly enhanced with Oracle9i Release2.
Database Validator has two distinct modes: one mode for Oracle8i and Oracle9i databases and
another mode for Oracle9i Release2 (and later) databases.
• Logical Volume Manager:
• VxVM (for the Solaris OS)
• LVM (for the HP-UX OS)
• LVM (for the AIX OS)
• Restrictions and Cautions:
• Only write Oracle data to a volume (LU) that is being checked by Database Validator.
• If an LU being checked by Database Validator has multiple paths, make sure that each path
is set as a target of checking.
• If host-based striping (for example, LVM with striping functionality) is used on an LU, then the
stripe size must be an exact multiple of the Oracle data block size for that LU.
Note: Versions other than those listed above may be supported in future enhancements. For the latest
information on supported OS and software versions, contact your HP representative.
Oracle Data Validation Service
In order to use Database Validator, you need to set up the hardware and software for Database
Validator in the storage system and the host server. Operations for these settings are provided as an
Oracle Data Validation Service and this service is required. For details, contact your HP representative.
• Restrictions and Cautions
• Oracle application:
• Make sure that the Oracle DB_BLOCK_CHECKSUM parameter is set to TRUE.
• Make sure that the Oracle application is set to run in the Archive Log mode.
• Oracle files:
• Raw devices: All Oracle tablespace files must be placed on raw volumes (including LVM
raw volumes). Database Validator does not support file system-based Oracle files.
• Data files separate from redo log files: The Oracle redo log files (including archive logs)
must be on different LUs than the data files (including control files). Make sure that the Oracle
redo log files and data files are not located on the same LU.
Since other files (archive log files) are not the target of the validation, no special consider-
ation is required for these files.
• Block size: Do not store Oracle data of different block sizes in the same LU. Make sure that
you write only the data of the same block size to the same LU.
• Restoring Oracle files: If in the past, the database was running without checksum enabled,
then old blocks without checksum information may exist on disk. If you need to restore Oracle
data files from a backup, you need to disable validation checking for those data files that
were backed up prior to Oracle checksum being enabled.
• Oracle on LVM (VxVM):
• If LVM is used, the LDEVs, after LVM mapping, must obey two separation rules: the
data/control files must be separate from the redo log files and must be the same block size.
• If LVM is used, configure the LUs before enabling Database Validator checking using XP
RAID Manager. The LVM performs some writes to disk as part of the configuration process.
XP24000/XP20000 Database Validator User's Guide 15