dbdst_convert(1M)

NAME

dbdst_convert - Convert volume based filesystem to DBDST ready MVS filesystem

SYNOPSIS

dbdst_convert -S ORACLE_SID -M mount_device

-v newvol,newvol,...

AVAILABILITY

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

lslpp -L VRTSdbed

DESCRIPTION

The dbdst_convert command is used to convert an existing volume based regular filesystem to DBDST ready MVS filesystem. The volume represented by the <mount_device> will be renamed to <mount_device>-b4vset. A new volume-set by name <mount_device> will be created. The old filesystem will be converted to MVS filesystem. The new volumes specified via argument newvol,newvol... will be added to the MVS. All but the last volume will be classified as PRIMARY storage class. The last volume of the MVS will be classified as SECONDARY storage class. At the completion of this command, the filesystem is ready for DBDST use. The database can be online when executing this command, but the database objects residing on this filesystem should be offlined using apprpriate SQL and the filesystem should be unmounted. After executing this command, DBA should online the concerned database objects which were offlined earlier after mounting the filesyste after mounting the filesystem. The first volume of the MVS filesystem meant for both metadata and datablocks. The second and subsequent volumes of the MVS are meant for datablocks only. DBA should make sure that the first volume has enough free space for all the filesstem metadata. The space usage can be seen by using dbdst_show_fs command.

OPTIONS

The following options are supported:
-S ORACLE_SID
  Specifies the name of the Oracle database whose information will be retrieved.
-M mount_device
  Specifies the block device where the file system resides. This should be of the form /dev/vx/dsk/<dgname>/<vsetname>
-v newvol,newvol,...
  Specifies the list of new volumes that will be added to the MVS

Real Application Clusters (RAC) Considerations

This command is supported in a RAC environment. This command can be run on any node of the RAC.

EXAMPLES

This example shows how to convert old volume based archivelog filesystem to a DBDST ready MVS filesystem on device /dev/vx/dsk/oradata/arch.

$ /opt/VRTS/bin/dbdst_convert -S PROD -M /dev/vx/dsk/oradata/arch \
-v vol3,vol4

NOTES

This command must be run as Oracle DBA user. This command can be executed when the database is online. Make sure the database objects residing on this filesystem are offline.

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

If the datbabase is configured for flashsnap, make sure the snapshots are resynced before running this command.

EXIT STATUS

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.

SEE ALSO

RAC is not supported with some SF products/configurations. For details please refer to the 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)

Storage Foundation: Storage and Availability Management for Oracle Databases


SF for Oracle dbdst_convert(1M)