Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

For example, sales are mostly catalog-driven for a large retailer specializing in
sports equipment. Product details are saved in a large database and the product
table is partitioned based on type of activity. Some of the products are seasonal
and do not sell well at other times. For example, very few snow skis are sold during
the summer. To achieve season-based migration, see the following example.
Assume the table product_tab has two partitions, summer and winter. Each of
these partitions is mapped to a separate data file.
First, you must set up your system to use SmartTier for Oracle.
To add the fast_storage and slow_storage storage classes
◆
Use the dbdst_admin command as follows:
$ /opt/VRTS/bin/dbdst_admin -S PROD -o addclass=\
fast_storage:"Fast Storage for Production DB"
$ /opt/VRTS/bin/dbdst_admin -S PROD -o addclass=\
slow_storage:"Slow Storage for Production DB"
To convert the database's file system and add volumes for use with SmartTier for
Oracle
◆
Use the dbdst_convert command as follows:
$ /opt/VRTS/bin/dbdst_convert -S PROD \
-M /dev/vx/dsk/oradg/oradata -v new_vol1,new_vol2,new_vol3
To classify volumes into storage classes
◆
Use the dbdst_classify command as follows:
$ /opt/VRTS/bin/dbdst_classify -S PROD \
-M /dev/vx/dsk/oradg/oradata -v new_vol1:fast_storage
$ /opt/VRTS/bin/dbdst_classify -S PROD \
-M /dev/vx/dsk/oradg/oradata -v new_vol2:slow_storage,\
new_vol3:slow_storage
Once the volumes are configured, an administrator can define file placement
policy rules that specify seasonal relocation of selected tablespaces and partitions
and assign them to the database’s file system.
SmartTier for Oracle use cases
SmartTier for Oracle file-based use cases
270