Performing Storage Rollback using dbed_ckptrollback
You can use the dbed_ckptrollback command to rollback an Oracle database to a Storage Checkpoint.
Before performing a Storage Rollback, the following conditions must be met:
Prerequisites
| -
You may be logged in as either the database administrator or superuser.
|
Usage notes
| -
The
dbed_ckptrollback command rolls an Oracle database back to a specified Storage Checkpoint. You can perform a Storage Rollback for the entire database, a specific tablespace, or list of datafiles.
Database rollback for the entire database requires that the database be inactive before Storage Rollback commences. The dbed_ckptrollback command will not commence if the Oracle database is active. However, to perform a Storage Rollback of a tablespace or datafile, only the tablespace or datafile to be rolled back must be offline (not the entire database).
-
You must run the
dbed_update command after upgrading to Storage Foundation 5.0 for Oracle RAC from a previous release. This will allow you to roll back to a Storage Checkpoint that was created with an earlier version of this product.
-
See the
dbed_ckptrollback(1M) manual page for more information.
|
To roll back an Oracle database to a Storage Checkpoint
To rollback a tablespace to a Storage Checkpoint
If the Oracle database is running, you must take the tablespace offline before running this command. If the tablespace is online, the command will fail.
In the case of an instant Storage Checkpoint, rolling back a tablespace does not apply.
To rollback datafiles to a Storage Checkpoint
-
Use the
dbed_ckptrollback command with the -F option as follows:
$ /opt/VRTS/bin/dbed_ckptrollback -S PROD \
-H /oracle/product/9i -F /share/oradata1/data01.dbf \
/share/oradata2/index01.dbf -c Checkpoint_903937870
If the Oracle database is running, you must take the datafile offline before running this command. If the datafile is online, the command will fail.
In the case of an instant Storage Checkpoint, rolling back datafiles does not apply.
