dbdst_obj_move - move the specified database objects like table, index or partition to the desired storage class.

dbdst_obj_move -S ORACLE_SID -H ORACLE_HOME

     [-v] -t <table name> [-s <start extent>] [-e <end extent>] -c storage-class

dbdst_obj_move -S ORACLE_SID -H ORACLE_HOME

     [-v] -i <index name> [-s <start extent>] [-e <end extent>] -c storage-class

dbdst_obj_move -S ORACLE_SID -H ORACLE_HOME

     [-v] -p <partition name> [-s <start extent>] [-e <end extent>] -c storage-class

Veritas Storage Foundation. To determine whether this product is installed on a Linux system, enter:

rpm -qa | grep VRTSdbed

The dbdst_obj_move command is used to move the specified database table, index or a partition files to the desired storage class. Oracle stores database objects in a container called tablespace. An Oracle tablespace is usually constructed of several datafiles. A database object like table/index has extents allocated from multiple datafiles. A given datafile usually contans extents from multiple database objects.

The dbdst_obj_move command queries oracle dba_extents catalog table and for each extent gets file offest and lengh in bytes. This command passes these offset/lenght information to VxFS low level SmartTier commands to move the database extents to desired storage class.

The underlying VxFS moves the filesystem blocks to target class one block at a time. The database can do active IO to these blocks while VxFS is moving these blocks. It is strongly advised to keep filesysemt block size same as Oracle database db_block_size.

Oracle stores catalog and other dictionary data in SYSTEM and SYSAUX tablespace. It is advised not use dbdst_obj_move to move objects in SYSTEM and SYSAUX tablespace. Please use dbdst_tbs_move or dbdst_file_move commands to relocate SYSTEM and SYSAUX tablespaces to different storage class.

During dbdst_obj_move of a TABLE, if there are lot of inserts to the TABLE, the underlying datafile may go through resize (autoextend). Since dbdst_obj_move gets DB extent information at the begining of the command, the autoextend blocks will not be moved to target class.

The following options are supported:

-S ORACLE_SID
	Specifies the name of the Oracle database whose information will be retrieved.
-H ORACLE_HOME
	Specifies the ORACLE_HOME for the database.
-v	This is an optional argument. If this option is specified, a verification will be done after moving each extent to the target storage class. If the target storage class, does not have enough free sapce, some the the table extents may not be moved.
-t table name	Name of the table which needs to be moved or relocated.
-i Index name	Name of the index which needs to be moved or relocated.
-p partition name
	Name of the partition which needs to be moved or relocated.More than one partitions can co-exiest in the same tablespace.
-c storage-class
	Specifies the storage class that the table/index extents will be moved to.
-s start-extent
	This option specifies the starting extent of the table/index which needs to be moved. The default starting extent is zero.
-e end-extent
	This option specifies the last extent of the table/index which needs to be moved. If this option is not specified, then complete table/index will be moved to target class.

This command is supported in a RAC environment. This command can be run on any n ode of the oracle RAC cluster. Since this command queries the Database, the instance need to be up where the command is executed.

Use following command to move entire emp table to SYMMETRIX. Move extents 100 to 400 of table emp to SSD. Move partition q1_orders to SSD and verify it.

$ /opt/VRTS/bin/dbdst_obj_move -S PROD -H /opt/oracle/home11g -t emp -c SYMMETRIX
$ /opt/VRTS/bin/dbdst_obj_move -S PROD -H /opt/oracle/home11g -t emp -s 100 -e 400 -c SSD
$ /opt/VRTS/bin/dbdst_obj_move -S PROD -H /opt/oracle/home11g -v -p q1_orders -c SSD

This command must be run as Oracle DBA user. This command must executed when the database is online.

dbed_update must be run at least once before this command to ensure an up-to-date repository.

0	Command executed successfully.
1	An Error Occured.
101	Licence check failed.
102	No license to execute this command.
103	Invalid Storage Class
104	The device or mount point is not owned by user
105	Could not get information from Oracle Database
255	Could not load program.

RAC is not supported with some SF products/configurations. For details please refer to the Veritas Storage Foundation: Storage and Availability Management for Oracle Databases Guide

dbdst_classify(1M), dbdst_admin(1M), dbdst_convert(1M), dbdst_file_move(1M), dbdst_partition_move(1M), dbdst_preset_policy(1M), dbdst_report(1M), dbdst_rmvol(1M), dbdst_show_fs(1M), dbdst_tbs_move(1M), dbdst_obj_move(1M), dbdst_obj_view(1M), oracle_edition(7)

Veritas Storage Foundation: Storage and Availability Management for Oracle Databases