HP StoreServ Application Suite for Oracle Media manual Database Volumes Under Veritas VxVM Control

Recovery Manager for Oracle User’s Guide

8.3 Database Volumes Under Veritas VxVM Control

If any of the database volumes are under Veritas VxVM control, perform the following procedures.

8.3.1Rollback with Read-Write Virtual Copies

1On both the backup host and the primary host:

a Shutdown both databases. For the cloned database on the backup host, you should perform log switches to make sure all online redo logs are switched to archive log files and that they are physically on the disk before you shutdown the cloned database. Or you can FTP over all online redo log files to the primary host, which can be used when performing database recovery.

b Manually unmount all file systems used by both databases. Do not use the vcdba_umount utility in this step, which not only unmounts the file systems, but also removes the read-write virtual copy from the InServ Storage Server. If ASM is being used, unmount all involved ASM disk groups.

c Deport the VxVM disk groups (used by datafiles and archive log destination). Example:

On the backup host:

vxdg deport orcl920dg_042903142921 vxdg deport arch920dg_042903142921

On the primary host:

vxdg deport orcl920dg vxdg deport arch920dg

Disk groups with trailing timestamps are created by Recovery Manager when performing a database backup. They can be found in the virtual copy repository.

2On the InServ Storage Server, remove the VLUNs used by datafiles and archive log destination by issuing the removevlun <vvname> <lun> <host> command.

8.4

Database Volumes Under Veritas VxVM Control