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.

Warning:

On AIX:

If the -o cio option was used with the mount command to mount your primary database file systems, Concurrent I/O will not be preserved when using dbed_clonedb to create a clone database.

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

Prerequisites

  • You must first create a Storage Checkpoint.

  • 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.

Usage notes

  • 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.

  • See the dbed_clonedb(1M) manual page for more information.

Limitations for Oracle RAC

  • When you clone the database by using Storage Checkpoint, the node can be any node in the same Oracle RAC cluster but the archive log destination is required to be on CFS file system. Otherwise, you must manually copy the archive log files.

Table: dbed_clonedb command options lists the options for the dbed_clonedb command.

Table: dbed_clonedb command options

Option

Description

-S CLONE_SID

Specifies the name of the new Oracle SID, which will be the name of the new database instance.

-m MOUNT_POINT

Indicates the new mount point of the Storage Checkpoint.

-c CKPT_NAME

Indicates the name of the Storage Checkpoint.

-o umount

Shuts down the clone database and unmounts the Storage Checkpoint file system.

-o restartdb

Mounts the Storage Checkpoint file system and starts the clone database. The -o restartdb option will not attempt to recover the clone database.

-d

Used with the -o umount option. If the -d option is specified, the Storage Checkpoint used to create the clone database will be removed along with the clone database.

-p

Specifies a file containing initialization parameters to be modified or added to the clone database's initialization parameter file prior to startup. The format of the pfile_modification_file is the same as that of the Oracle initialization parameter file.

To clone an Oracle instance

To shut down the clone database and unmount the Storage Checkpoint

To mount a Storage Checkpoint file system and start the clone database

To delete a clone database and the Storage Checkpoint used to create it

More Information

Creating Storage Checkpoints using dbed_ckptcreate