Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

Some database changes made after a Storage Checkpoint was taken may make it
impossible to perform an incomplete recovery of the databases after Storage
Rollback of an online or offline Storage Checkpoint using the current control files.
For example, you cannot perform an incomplete recovery of the database to the
point right before the control files have recorded the addition or removal of
datafiles.
Warning: Use extreme caution when recovering your database using alternate
control files.
Suppose a user deletes a table by mistake right after 4:00 p.m., and you want to
recover the database to a state just before the mistake. You created a Storage
Checkpoint (Checkpoint_903937870) while the database was running at 11:00
a.m., and you have ARCHIVELOG mode enabled.
To recover the database using a Storage Checkpoint
1
As root, freeze the cluster service group for the database.
# hagrp -freeze Service_Group
2
Ensure that the affected datafiles, tablespaces, or database are offline.
3
Use storage rollback to roll back any datafiles in the database that contained
the table data from the Storage Checkpoint you created at 11:00 a.m.
For example:
$ /opt/VRTS/bin/dbed_ckptrollback -S $ORACLE_SID -H\
$ORACLE_HOME -c Checkpoint_903937870
For other examples of this command (for a database, tablespace, or datafile):
See “Performing Storage Rollback using dbed_ckptrollback” on page 219.
4
Start up the database instance if it is down.
5
Unfreeze the service group.
# hagrp -unfreeze Service_Group
Using Database Storage Checkpoints and Storage Rollback
Backing up and recovering the database using Storage Checkpoints
206