Veritas Storage Foundation for Oracle 5.0 Administrator's Guide, HP-UX 11i v3, Second Edition, December 2008

product_tab, and uses underlying DST services to immediately relocate those files
to the fast_storage and slow_storage placement classes respectively.
To move winter data to slower storage and summer data to faster storage at the
beginning of summer
◆
Use the dbdst_partition_move command as follows:
$ /opt/VRTS/bin/dbdst_partition_move -S PROD -T product_tab \
-p summer -c fast_storage
$ /opt/VRTS/bin/dbdst_partition_move -S PROD -T product_tab \
-p winter -c slow_storage
Database Dynamic Storage Tiering formulates DST policy rules that
unconditionally relocate the files containing the target partitions to the destination
placement classes. It merges these rules into the database file system’s active
policy, assigns the resulting composite policy to the file system, and enforces it
immediately to relocate the subject files. Because the added policy rules precede
any other rules in the active policy, the subject files remain in place until the
dbdst_partition_move command is next executed, at which time the rules are
removed and replaced with others.
Scheduling the relocation of archive and Flashback logs
Because they are the primary mechanism for recovering from data corruption,
database logs are normally kept on premium storage, both for I/O performance
and data reliability reasons. Even after they have been archived, logs are normally
kept online for fast recovery, but the likelihood of referring to an archived log
decreases significantly as its age increases. This suggests that archived database
logs might be relocated to lower-cost volumes after a certain period of inactivity.
Similarly, Veritas Storage Foundation for Oracle Flashback technology creates
logs that can be used for quick recovery from database corruption by restoring a
database to its state at a previous time. Flashback logs are normally kept for a
shorter period than archived database logs, If used at all, they are typically used
within a few hours of creation. Two or three days is a typical Flashback log lifetime.
The rapidly decaying probability of use for archive and Flashback logs suggests
that regular enforcement of a placement policy that relocates them to lower-cost
storage after a period of inactivity can reduce an enterprise’s average cost of
online storage.
For example, a customer could be using a large OLTP Oracle database with
thousands of active sessions, which needs to be up and running 24 hours a day
and seven days a week with uptime of over 99%, and the database uses Flashback
201Using Database Dynamic Storage Tiering
Database Dynamic Storage Tiering use cases for Oracle