Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

Once the assigned policy is deleted, the allocation for metadata and file data for
subsequent requests of storage checkpoint will return to the no policy assigned
state.
For VxFS file systems disk layout Version 7, the volumes on the VxFS Multi-Volume
File System can be either one of these types: dataonly and metadataok. Only
metadataok volumes can be used to store checkpoint metadata. By default, only
the first volume that is being added to the VxVM volume set is a metadataok
volume. This means only the first volume that is being added to the VxVM volume
set can be specified in the ckpt_metadata_policy by default. Use the following
file system command to change the default setting. To check the flags of each
volume in a VxFS Multi-Volume File System, execute the following file system
command as root:
/opt/VRTS/bin/fsvoladm queryflags mountpoint
To change a dataonly volume to a metadataok volume, execute the following file
system command as root:
/opt/VRTS/bin/fsvoladm clearflags dataonly mountpoint
vol-name
The following are usage notes for Storage Checkpoint allocation policies:
Since the Storage Checkpoint allocation policies feature is
associated with the MVS file system, it is available only on file
systems using disk layout Version 6 and beyond.
Storage Checkpoint allocation policy requires VxVM Volume Set
and VxFS Multi-Volume File Systems features to be enabled. These
features are included in the Enterprise Edition of Storage
Foundation.
See the Multi-Volume File System chapter in the Veritas File System
Administrator's Guide for creating Volume Sets and MVS file
systems for the primary file systems used by the database datafiles.
Data allocation is done by the volumes in the order that was
assigned in the policy.
The maximum length of a Storage Checkpoint allocation policy
name is 64 characters.
Usage notes
Using Storage Checkpoint allocation policies
You can use the dbed_ckptpolicy command to manage Storage Checkpoint
allocation policies.
155Using Storage Checkpoints and Storage Rollback
Storage Checkpoint allocation policies