Search <book_title>...

Veritas InfoScale™ 8.0.2 Storage and Availability Management for Oracle Databases - AIX, Linux, Solaris

Last Published: 2023-06-12

Product(s): InfoScale & Storage Foundation (8.0.2)

Platform: AIX,Linux,Solaris

Section I. Storage Foundation High Availability (SFHA) management solutions for Oracle databases
1. Overview of Storage Foundation for Databases
Section II. Deploying Oracle with Veritas InfoScale products
Section III. Configuring Storage Foundation for Database (SFDB) tools
1. Configuring and managing the Storage Foundation for Databases repository database
2. Configuring authentication for Storage Foundation for Databases (SFDB) tools
Section IV. Improving Oracle database performance
Section V. Using point-in-time copies
Section VI. Optimizing storage costs for Oracle
Section VII. Managing Oracle disaster recovery
1. Using Storage Foundation for Databases (SFDB) tools in a replicated environment
2. Using volume snapshots in a replicated environment
Section VIII. Storage Foundation for Databases administrative reference
Section IX. Reference

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

Use the dbed_clonedb command as follows:

$/opt/VRTS/bin/dbed_clonedb -S new2 -m /tmp/new2 \
-c onCkpt
SFDB vxsfadm WARNING V-81-0962 dbed_clonedb will
 be deprecated in the next release
SFDB vxsfadm WARNING V-81-0963 As an alternative
use /opt/VRTS/bin/vxsfadm
Creating Storage Checkpoint onCkpt_rw_1378467816 ... Done
Storage Checkpoint onCkpt_rw_1378467816 created
Mounting Checkpoint to /tmp/new2...                            Done
Cloning the Pfile ...                                          Done
Mounting the database...                                       Done
Recovering the clone database...

To shut down the clone database and unmount the Storage Checkpoint

Use the dbed_clonedb command as follows:

$ /opt/VRTS/bin/dbed_clonedb -S new2 -o umount
SFDB vxsfadm WARNING V-81-0962 dbed_clonedb will
be deprecated in the next release
SFDB vxsfadm WARNING V-81-0963 As an alternative
use /opt/VRTS/bin/vxsfadm
Shutting down the clone database new2... Done
Unmounting the checkpoint... Done

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

Use the dbed_clonedb command as follows:

$/opt/VRTS/bin/dbed_clonedb -S new2 -o restartdb
SFDB vxsfadm WARNING V-81-0962 dbed_clonedb will be
 deprecated in the next release
SFDB vxsfadm WARNING V-81-0963 As an alternative use
 /opt/VRTS/bin/vxsfadm
Mounting Checkpoint to /tmp/new2... Done
Mounting the database... Done
Starting the Clone database ... Done

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

Use the dbed_clonedb command as follows:

$ /opt/VRTS/bin/dbed_clonedb -S new2 -o umount -d
SFDB vxsfadm WARNING V-81-0962 dbed_clonedb will be
 deprecated in the next release
SFDB vxsfadm WARNING V-81-0963 As an alternative use
 /opt/VRTS/bin/vxsfadm
Shutting down the clone database new2... Done
Unmounting the checkpoint... Done
Deleting the Checkpoint onCkpt_rw_1316003740...
Deleting Checkpoint from /db01... Done

More Information

Creating Storage Checkpoints using dbed_ckptcreate