Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)
See “Administering SmartTier at the sub-file level” on page 266.
Relocating old table data to a lower cost or secondary tier
In some databases such as TELCO applications, call detail records (CDR) accumulate
very quickly. For regulatory purposes, these records must be saved for several
years, causing the size of the database to grow at an enormous rate. If the CDR
table is partitioned, the old partitions can be relocated to the lower cost tier.
However, if the CDR table is not partitioned, alternatives are needed. One potential
alternative is described below.
The extents for CDR tables are allocated on demand. This means extent 100 is
created much earlier than extent 900. It also means that the activity for CDR
records in extent 100 is less. From the extent-id, using dba_extents and
dba_segments dictionary tables, file, offset, length information can be generated.
From this information, you can relocate the identified portion of the file to the
secondary tier.
To relocate old table data to a lower cost or secondary tier
1
Identify the less active objects or segments of the database using an Oracle
AWR report.
2
Determine the storage tier to which the less active objects or segments can
be relocated.
3
To ensure an up-to-date SFDB repository, run dbed_update.
4
Run the command to move the table CDR_100 to tier-2.
$ dbdst_obj_move -S PROD -H /ora11ghome -t CDR_100 -c tier-2
The command in the example below displays the set datafiles where the specified
table/index resides. If the underlying file system is a multi-volume file system, it
will display the corresponding volume and tier name.
To verify that the database segment is relocated to the correct tier
◆
Run the command to view the relocated table:
$ dbdst_obj_view -S PROD -H /ora11ghome -o CDR_100
For more on using the dbdst_obj_move command:
See “Administering SmartTier at the sub-file level” on page 266.
SmartTier for Oracle use cases
SmartTier for Oracle sub-file use cases
278