Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

started as a single instance on the node on which the dbed_clonedb command is
executed.
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, review the following information:
■ You must first create a Storage Checkpoint.
See “Creating Storage Checkpoints using dbed_ckptcreate”
on page 328.
■ You must be logged in as the database administrator.
■ Make sure you have enough space and system resources to create
a clone database on your system.
■ A clone database takes up as much memory and machine resources
as the primary database.
■ In a Veritas Storage Foundation for Oracle RAC environment, the
archive log destination is required to be on a Veritsa Cluster File
System file system.
Prerequisites
■ This command is supported by Veritas Storage Foundation for
Oracle RAC.
■ In a Veritas Storage Foundation for Oracle RAC environment,
cloning an Oracle database with an instant Storage Checkpoint is
not supported.
■ The dbed_clonedb command is used to create a copy of a
database, cloning all existing database files to new locations.
■ The ORACLE_SID and ORACLE_HOME environment variables must
be set to the primary database.
■ It is assumed that the user has a basic understanding of the
database recovery process.
■ See the dbed_clonedb(1M) manual page for more information.
Usage notes
Table A-3 lists the options for cloning the Oracle database.
Veritas Storage Foundation for Oracle Command Line Interface
About the command line interface
344