Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

Unmounting a Storage Checkpoint
To unmount a Storage Checkpoint for an Oracle database, use the dbed_ckptumount
command as follows:
◆
$ /opt/VRTS/bin/dbed_ckptumount -S ORACLE_SID -c CKPT_NAME \
[ -m MOUNT_POINT ] [ -h ]
See the dbed_ckptumount(1M) manual page for more information.
Recovering a database using a Storage Checkpoint
Becasue Storage Checkpoints record the before images of blocks that have changed,
you can use them to do a file-system-based storage rollback to the exact time when
the Storage Checkpoint was taken. You can consider Storage Checkpoints as
backups that are online, and you can use them to roll back an entire database, a
tablespace, or a single database file. Rolling back to or restoring from any Storage
Checkpoint is generally very fast because only the changed data blocks need to
be restored.
Note: 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 incomplete recovery of the database
to the point right before the control files have recorded the addition or removal
of datafiles. To provide recovery options, a backup copy of the control file for the
database is saved in a temporary location when Storage Checkpoint rollback is
performed. 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.
169Using Storage Checkpoints and Storage Rollback
Backing up and recovering the database using Storage Checkpoints