VERITAS Storage Foundation 4.1 Oracle Administrator's Guide

Managing Snapshots with Database FlashSnap Prerelease 8 September 2005, 8:55am
312 VERITAS Storage Foundation for Oracle Administrator’s Guide
Note Force snapshot creation can be used after a snapshot operation has failed and the
problem was fixed without using VERITAS Storage Foundation for Oracle commands.
(That is, the volumes were synchronized without using VERITAS Storage Foundation
for Oracle commands.) In this situation, the status of the snapplan will appear as
unavailable for creating a snapshot. The Force snapshot creation option ignores the
unavailable status, checks for the availability of volumes, and creates the snapshot after
the volumes pass the availability check.
5. Click Finish to continue.
6. If the snapshot creation was successful, you will receive a confirmation message.
7. Click the Show details checkbox to view the actions taken. You should see information similar
to the following:
dbed_vmsnap started at 2004-05-13 17:09:40
VxDBA repository is up to date.
The database is running in archivelog mode.
A snapshot of ORACLE_SID PROD is in DG SNAP_PRODdg.
Snapplan sp2 is used for the snapshot.
VxDBA repository volume is SNAP_ORACLE1.
If -r <relocate_path> is used in dbed_vmclonedb,
make sure <relocate_path> is created and owned by
Oracle DBA. Otherwise, the following mount points
need to be created and owned by Oracle DBA:
/prod_db.
/oracon.
dbed_vmsnap ended at 2003-05-13 17:10:29
Click OK to continue.
You can now use the snapshot as a database backup.
Note You will need this information when you start your snapshot database.
Creating a Clone Database With a Snapshot
After having created a snapshot, you can use the snapshot to create a clone database. The cloned
database can be used for decision-making and testing that cannot be done on your production
database.