You can clone a pluggable database (PDB) to a different or same target CDB on the same host or alternate host. You can also recover the cloned PDB to a desired SCN or date and time.
For this field... | Do this... |
---|---|
Clone host | By default, the source database host is populated. If you want to create the clone on an alternate host, select the host having the same version of Oracle and OS as that of the source database host. |
Target CDB | Select the CDB where you want to include the cloned PDB. You should ensure that the target CDB is running. |
Database State | Select the Open the PDB to be cloned in READ-WRITE mode checkbox if you want to open the PDB in READ-WRITE mode. |
Datafile locations | By default, the datafile location is populated. The SnapCenter default naming convention for SAN or NFS file systems is FileSystemNameofsourcedatabase_SCJOBID. The SnapCenter default naming convention for ASM disk groups is SC_HASHCODEofDISKGROUP_SCJOBID. The HASHCODEofDISKGROUP is an automatically generated number (2 to 10 digits) that is unique for each ASM disk group.
Note: If you are customizing the ASM disk group name, ensure that the name length adheres to the maximum length supported by Oracle.
If you want to specify a different path, you must enter the datafile mount points or ASM disk group names for clone database. |
Click Reset to get the default database parameter settings.
Field name | Description |
---|---|
Until Cancel | SnapCenter performs recovery by mounting the latest log backup having the unbroken sequence of archive logs after that data backup that was selected for cloning. The log and data backup should be on primary storage to perform the clone on primary storage and log and data backup should be on secondary storage to perform the clone on secondary storage. The cloned database is recovered till the missing or corrupt log file. |
Date and time | SnapCenter recovers the database up to a specified date and time. Note: The time can be specified in 24 hour format.
|
Until SCN (System Change Number) | SnapCenter recovers the database up to a specified system change number (SCN). |
Specify external archive log locations | Specify the external archive log location. |
Create new DBID | By default Create new DBID check box is selected to generate a unique number (DBID) for the cloned database differentiating it from the source database. Clear the check box if you want to assign the DBID of the source database to the cloned database. In this scenario, if you want to register the cloned database with the external RMAN catalog where the source database is already registered, the operation fails. |
Enter sql entries to apply when clone is created | Add the sql entries that you want to apply when the clone is created. |
Enter scripts to run after clone operation | Specify the path and the arguments of the postscript that you want to run after the clone operation. You should store the postscript either in /var/opt/snapcenter/spl/scripts or in any folder inside this path. By default, the /var/opt/snapcenter/spl/scripts path is populated. If you have placed the script in any folder inside this path, you need to provide the complete path up to the folder where the script is placed. |
If you want to create a backup of the cloned PDB, you should backup the target CDB where the PDB is cloned because backing up only the cloned PDB is not possible. You should create a secondary relationship for the target CDB if you want to create the backup with secondary relationship.
In a RAC setup the storage for cloned PDB is attached only to the node where the PDB clone was performed. The other nodes of the RAC are in MOUNTED state. If you want the cloned PDB to be accessible from the other nodes, you should manually attach the storage to the other nodes.