Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

■ 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.
Prerequisites
■ 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.
■ In an Oracle RAC configuration, the clone database is started as a
single instance on the mode where the dbed_clonedb command
is executed.
■ Cloning an Oracle RAC database with an instant storage checkpoint
is not supported.
■ 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
Options for the dbed_clonedb command are:
Table 9-1
dbed_clonedb command options
DescriptionOption
Specifies the name of the new Oracle SID, which will be the
name of the new database instance.
-S CLONE_SID
Indicates the new mount point of the Storage Checkpoint.-m MOUNT_POINT
Indicates the name of the Storage Checkpoint.-c CKPT_NAME
Runs the command in interactive mode where you must
respond to prompts by the system. The default mode is
non-interactive. (Optional)
-i
Shuts down the clone database and unmounts the Storage
Checkpoint file system.
-o umount
Mounts the Storage Checkpoint file system and starts the
clone database. The -o restartdb option will not attempt
to recover the clone database.
-o restartdb
171Using Storage Checkpoints and Storage Rollback
Cloning the Oracle instance using dbed_clonedb