Recovery Manager for Oracle User’s Guide

8.1 vcdba_rollback Usage

Refer to vcdba_rollback on page 6.35 for the syntax and available options for the vcdba_rollback command.

The procedure to rollback the data volumes depends on the data type of the datafile. If the datafiles are composed from Veritas VxVM then special VxVM procedures apply.

8.2 Database Volumes Not Under Veritas VxVM Control

If none of the disk volumes used by a database are under Veritas VxVM control, perform the following procedures.

8.2.1Rollback with Read-Only Virtual Copies

1On the primary host, shutdown the database if it is up and running. If ASM is being used, unmount all involved ASM disk groups.

2On the primary host, unmount all file systems where the database volumes are mounted.

3On the InServ Storage Server, remove the VLUNs for the data volumes by issuing the removevlun <vvname> <lun> <host> command.

Example:

removevlun Oracle_data1 101 pilot

4Keep the list of the VLUNs, which are removed by the command above. The VLUNs are used to re-export the LUNs with the same disk IDs after rollback operation is completed.

5From the backup host, execute the vcdba_rollback -s <oracle_sid> -p <primary_host> -t <timestamp> -vcommand to roll back the read-only copy:

Example:

vcdba_rollback -s TEST920 -p pilot -t 042903142921 -v

6On the InServ Storage Server, export all the data volumes to the primary host with the same VLUNs saved in step 4 by issuing the createvlun <vvname> <lun> <host> CLI command:

8.2

vcdba_rollback Usage

Page 162
Image 162
HP StoreServ Application Suite for Oracle Media manual Vcdbarollback Usage, Database Volumes Not Under Veritas VxVM Control