In order to clone successfully, the following requirements must be met
There are some prerequisites for cloning PDBs and converting nonCDBs to PDBs by cloning:
The target CDB must be created in advance if you want to clone into a new CDB.
The source CDB or NonCDB and the target CDB must be running at least release 12.1.0.2.
The source CDB or NonCDB and the destination CDB require the same block size.
For cloning in live mode, the australia telegram screening source CDB or NonCDB and the target CDB must be running in archive log mode and at least on release Databases on release 12.1.x or databases running in no archive log mode must switch to read-only mode. This results in downtime.
The database options used, such as Oracle Text or Multimedia, must be the same between the source CDB or NonCDB and the target CDB.
The licensing limitations of the multitenant option must be observed. If multitenant was not purchased with the Enterprise Edition license, there can be a maximum of 3 PDBs in a CDB (template PDBs excluded). The standard edition is limited to 3 PDBs per CDB; multitenant cannot be licensed here. An existing PDB is cloned in up to 4 steps.
Below, three scenarios are presented on how PDBs can be cloned. In addition to the three scenarios, two upgrade scenarios are shown that use PDB cloning.
The cloning process of an existing PDB into the same CDB is completed in a maximum of 4 steps: If the PDB to be cloned is running in a CDB with release 12.2 or higher and in archive log mode, steps 1 and 4 can be omitted.