Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

5
In the add_tf.$ORACLE_SID.sql file, edit the sizes and default path names
of the tempfiles as needed to reside on cloned volumes configured for database
storage.
Note: Do not run the script without first editing it because path names may
not exist and the specified mount points may not contain sufficient space.
6
After you have modified the add_tf.$ORACLE_SID.sql script, execute it
against your clone database.
7
After you have successfully run the script, you may delete it.
Resynchronizing your database to the snapshot
If your database becomes corrupted, you can use reverse resynchronization to
recover the database from a clone. The reverse resynchronization feature of
Veritas Database FlashSnap enables you to resynchronize the primary database
or volume with a clone database or snapshot volume.
Note: In Veritas Storage Foundation for Oracle RAC configurations, the reverse
resynchronization option is not supported.
Reverse resynchronization requires the primary database to be offline so that it
remains unchanged.
Warning: After completing a reverse resynchronization, the content of the original
database is discarded. Storage Checkpoints taken on the original database or the
clone database before or after the snapshot was created are discarded. The
dbed_vmsnap -o reverse_resync_commit command cannot be undone and should
be used with extreme caution.
Before resynchronizing a database to a snapshot, make sure the following
conditions have been met:
287Using Database FlashSnap for backup and off-host processing
Resynchronizing your database to the snapshot