dbdst_file_move - move the specified database object or a specific list of files to the desired storage class if they have not been accessed for certain period.

dbdst_file_move -S ORACLE_SID

     -o { archive[n]|flashback } -c storage-class:days

dbdst_file_move -S ORACLE_SID

     -o external -f spec-file -c storage-class:days

dbdst_file_move -S ORACLE_SID

     -o datafile -f spec-file -c storage-class

dbdst_file_move -S ORACLE_SID

     -o { archive[n]|flashback } -R

dbdst_file_move -S ORACLE_SID

     -o external -f spec-file -R

AVAILABILITY

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

rpm -qa | grep VRTSdbed

The dbdst_file_move command is used to move the specified database object or a specific list of files to the desired storage class if they have not been accessed for certain period. For datafiles, this command relocates the specified files in spec-file into the desired storage-class immediately. For archive and external files, this command schedules a sweep task to be executed at sweeptime specified via dbdst_admin. For external files and datafiles, all the files and directories included in the spec-file should reside on a single filesystem. The archive[n], should corrospond to archive1 to archive10 and corrosponding LOG_ARCHIVE_DEST_N value from v$archive_dest will be taken. This archive_dest path must be valid and active. The database must be ARCHIVE mode as indicated by v$database view. For flashback, database version must be 10gR1 and above.

The following options are supported:

-S ORACLE_SID
	Specifies the name of the Oracle database whose information will be retrieved.
-o archive[n]
	Specifies to move the archive log files. The values must be archive1 to archive10. These corresponds to log_archive_destN from v$archive_dest view. This option should not be used together with the -f option. The storage class specified should be of the form -c <starage_class>:<days>.
-o flashback	Specifies to move flashback log files. This option is supported for Oracle version 10gR1 and beyond only. This option should not be used together with the -f option. The storage class specified should be of the form -c <starage_class>:<days>.
-o external	Specifies to move external files or datafiles. This option should be used together with -f option. The storage class specified should be of the form -c <starage_class>:<days>.
-o datafile	This option specifies to do a immediate relocation of datafiles specified in spec-file to the desired class.This option should be used together with -f option. The storage class specified should be of the form -c <starage_class> only.
-f spec-file	Specifies a filename which contains a list of files or directories to move. The command will check the access right of each file specified in listfile before actually moving the files. If caller of this command does not have access right on any of the file specified in the listfile, command will exit with error. This option should not be used together with the -o {archive | flashback}.
-c storage-class:days
	Specifies the storage class that the files will be moved to. If days is supplied, it will be moved to class if file has not been accessed in days number of days.
-R	This option specifies to remove the current DBDST policy on archive, flashback, datafile or external file.

This command is supported in a RAC environment. This command can be run on any node of the RAC. In case of RAC, a common archive log destination for all instances using clustered file system is recommended. If each instance has local archivelog destinations, this command needs to be run on a node where the corrosponding archive destination is local.

Use following command to move archivelogs older than 7 days at LOG_ARCHIVE_DEST_1 to storacle tier SECONDARY. The next example shows moving flashback logs older than 2 days to SECONDARY tier.

$ /opt/VRTS/bin/dbdst_file_move -S PROD -o archive1 SECONDARY:7
$ /opt/VRTS/bin/dbdst_file_move -S PROD -o flashback SECONDARY:2

This command must be run as Oracle DBA user. This command can be 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