HP 3PAR Application Software Suite for Oracle - Manual (Page 121)

# vxvol -g myvxvmdb_datadg startall
- For HP-UX logical volume groups, using the tmpfile generated during vgexport:
# vgimport -m pvname1, pvname2, ...
# vgchange -a y
Example:
# vgimport -m /tmp/lvmtest_datadg.map lvmtest_datadg /dev/disk/disk68
/dev/disk/disk69
vgchange -a y lvmtest_datadg
- For Linux logical volumes:
# vgscan
# vgimport
# lvchange -ay /dev/ /
Example:
# vgscan
# vgimport rh6lvm-datavg
# lvchange -ay /dev/rh6lvm-datavg/lvol0
# lvchange -ay /dev/rh6lvm-datavg/lvol1
Example:
# vxdg import
# vxvol -g startall
10. From the backup server, if needed, mount the file systems if the read-write virtual copy contains
file systems.
Example:
# mount -F vxfs /dev/vx/dsk/datadg/datavol/oradata
11. From the backup server, if needed, mount database ASM disk groups if ASM is in use and
contained in the read-write virtual copy volumes
Example:
SQL>alter diskgroup mount;
12. From the backup server, bring up the clone database if needed.
NOTE: Use with the -f option if the database virtual volumes are in Remote Copy groups.
Make sure that the related Remote Copy groups are stopped prior to running rmora_rollback
command.
Database Recovery after Rollback
The database was rolled back using a snapshot, it acted like the database was restored from a
previous backup image, if your control files were lost, you need to recover the database from your
backup control file.
You have two options to recover the database using the backed up control file as indicated at the
end of rmora_rollback command:
(backed up control file location: /etc/3par/solutions/
database server name>/)
Option:1 Using binary control file
Copy the binary control file to its original location for the primary database, and you can find out
the multiplexed control file locations by the following sample commands with example:
•
SQL> startup nomount;
•
SQL> show parameter control_files
rmora_rollback Usage 121