Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

To recover the database using a Storage Checkpoint

Ensure that the affected datafiles, tablespaces, or database are offline, and

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.

$ /opt/VRTS/bin/dbed_ckptrollback -H /oracle/product/9i -S PROD \

-c Checkpoint_903937870

Start up the database instance if it is down.

Use recover database until cancel, recover database until change,

or recover database until time to re-apply archive logs to the point before

the table was deleted to recover the database to 4:00 p.m.

Open the database with alter database open resetlogs.

Delete the Storage Checkpoint you created at 11:00 a.m. and any other Storage

Checkpoints created before that time.

Create a new Storage Checkpoint.

Cloning the Oracle instance using dbed_clonedb

You can use the dbed_clonedb command to clone an Oracle instance using a

Storage Checkpoint.

Cloning an existing database using a Storage Checkpoint must be done on the

same host. However, you can clone on any host within an Oracle RAC database

cluster.

You have the option to manually or automatically recover the database when

using the dbed_clonedb command:

■ Manual (interactive) recovery, which requires using the -i option, of the clone

database allows the user to control the degree of recovery by specifying which

archive log files are to be replayed.

■ Automatic (non-interactive) recovery, which is the default usage of the

command, recovers the entire database and replays all of the archive logs. You

will not be prompted for any archive log names.

Before cloning the Oracle instance, the following conditions must be met:

Using Storage Checkpoints and Storage Rollback

Cloning the Oracle instance using dbed_clonedb

170