HP XP RAID Manager Software - Manual (Page 166)

Restrictions on Database Validator
•
Oracle tablespace location
File system-based Oracle files are not supported by Database Validator. All Oracle
tablespace files must be placed on raw volumes (including LVM raw volumes) directly. ◦
◦ If host-based striping is used on raw volumes, then the stripe size must be an exact multiple
of the Oracle block size.
◦ Oracle redo log files (including archive logs) must be on separate volumes with respect
to the data files (including control files). In other words, Oracle redo log files and the
data files must not be mixed on the same LU.
•
Restoring Oracle files
◦ Before restoring Oracle data files from a backup, data validation may need to be
temporarily turned off for those data files that were backed up prior to the Oracle checksum
being enabled.
Old blocks may exist on disk without checksum information in them if the database was running
without checksum enabled in the past.
•
Oracle on LVM(VxVM)
◦ LVM block size must be a multiple of the Oracle block size. The Oracle block size must
be less than or equal to the minimum of the LVM stripe size and the largest block size at
which LVM will not fracture (known as “Logical Track Group” in LVM), which is 256 KB
in LVM.
◦ When adding new physical volumes (PVs) to a logical volume (LV) to be used as an
Oracle data file, control file, or online log, the data validation should be re-enabled in
order to have HARD checking take effect on those new PVs.
Similarly, in order to have HARD checking no longer performed on PVs that have been removed
from an LV that had previously been used by Oracle, HARD checking should be explicitly disabled
on the device corresponding to the PV.
•
If host-based mirroring is used such as LVM mirroring, all component PV mirrors must be
HARD-enabled, otherwise the entire logical volume (LV) is exposed. That is, if a user takes
166 Data protection operations with RAID Manager