Home > Veritas Storage Foundation™ for Oracle Manual Pages
dbed_clonedb -S CLONE_SID -m MOUNT_POINT [-h] [-i]
-c CKPT_NAME [-p pfile_modification_file]
To unmount or restart a clone database:
dbed_clonedb -o umount | restartdb [-d] [-h]
lslpp -L VRTSdbed
To use dbed_clonedb, the current environment must be configured correctly for the primary database. This means that the ORACLE_SID and ORACLE_HOME environment variables must be set correctly for the primary database. Be sure you have enough space to create a clone database on your system. For Oracle RAC database, the archive log destination is required to be on Veritas Cluster File System.
dbed_clonedb brings up a mounted, writable clone of an Oracle instance. The new instance is given a new name and mount point, as specified by arguments to the command. The mount point should be identical to that used to mount the Storage Checkpoint. The dbed_clonedb command is designed to work with a mounted, writable Storage Checkpoint of an Oracle instance. If the Storage Checkpoint has not been mounted (for example, using the dbed_ckptmount command), dbed_clonedb will automatically mount the Storage Checkpoint as read-write at the specified mount point. The new Oracle instance is given a new name, and datafiles are on a new location, as specified by arguments to dbed_clonedb.
For online and instant Storage Checkpoints, all available archive logs will be played back for the recovery process. If the -i option is specified, dbed_clonedb will prompt you to complete the Oracle recovery process with the new database. This allows you the option of performing point-in-time recovery. For information about Oracle recovery, see the Oracle Backup and Recovery Guide for your version of Oracle.
For additional information about instant Storage Checkpoints, see dbed_ckptcreate(1M).
For instant Storage Checkpoints, dbed_clonedb uses the online redo logs for database recovery. Rolling forward is not allowed for instant Storage Checkpoints. For instant Storage Checkpoints, only database-level (including control files and redo logs) rollback is allowed. Individual datafiles and tablespaces cannot be rolled back. Cloning an Oracle RAC database with an instant Storage Checkpoint is not supported.
dbed_clonedb is designed to work with VxFS file systems or CFS file systems, and mounted Storage Checkpoints. Other types of file system are not supported by dbed_clonedb.
The -p pfile_modification_file allows modification to the memory-related parameters of the clone database's initialization parameter file. See the Administrator's Guide for the complete list of parameters that may be modified. The format of the pfile_modification_file is the same as the Oracle initialization parameter file. Any parameter matching one found in the primary database's initialization parameter file will be replaced with the corresponding value from the pfile_modification_file. Any parameter not found will be added to the clone database's pfile.
For a database located on a mounted Storage Checkpoint, dbed_clonedb assumes that the files that Oracle will attempt to open during the cloning process will be the originals. Because of this, you should change all symbolic links pointing to datafiles to relative links. The dbed_clonedb command examines Oracle datafiles for symbolic links that point to an absolute destination. If it finds absolute links, dbed_clonedb exits immediately with an error message. See the ln online manual page for more information about symbolic links.
The ORACLE_SID and ORACLE_HOME environment variables must be set correctly to use dbed_clonedb. If they are not set, then the dbed_clonedb command will not run.
When aborting a cloning operation, rerun the script as follows:
$ /opt/VRTS/bin/dbed_clonedb -S clone -m /local/oracle9/1 \.br -c Checkpoint_988813047 -i
To clone an Oracle database with automatic Oracle recovery:
$ /opt/VRTS/bin/dbed_clonedb -S clone -m /local/oracle9/1 \.br -c Checkpoint_988813047
Veritas Storage Foundation for Oracle Administrator's Guide
Veritas Storage Foundation for Oracle RAC Installation and Configuration Guide
Oracle Backup and Recovery Guide
Last updated: 15 Jan 2005
Copyright ©2009 Symantec Corporation
All rights reserved.