Oracle Database 12c Release 2 (12.2) introduced the ability to perform a hot clone of a remote pluggable database (PDB) using the command. In Oracle 19c it's possible to perform a remote clone of a pluggable database (PDB) using the Database Configuration Assistant (DBCA). - Prerequisites - Remote Clone a PDB with the DBCA - Appendix Related articles. Connect to the remote CDB and prepare it for cloning. Create a user in the remote database for use with the database link. In this case, we will use a common user in the remote PDB. Unlike a regular remote clone, we don't need to create a database link. We just need to supply the credentials we would use to create the link. The DBCA does the rest. Check the remote CDB is in local undo mode and archivelog mode. Because the remote CDB is in local undo mode and archivelog mode, we don't need to turn the remote database into read-only mode. Connect to the local CDB and prepare it for cloning. Check the local CDB is in local undo mode and archivelog mode. In 19c the DBCA command has a new parameter called , allowing us to create a new PDB by remote cloning an existing PDB. You can see the full syntax for the command here , although at the time of writing the documentation doesn't match the utility usage presented by the command. Make sure the environment is set up to point to the local instance "cdb1" and create a new PDB called "pdb5new" as a clone of the remote PDB called "pdb5" in the "cdb3" instance. Connect to the local root container and check the status of the new PDB. We can clean up by deleting the new pluggable database using the command below. The instances and pluggable databases used in these examples are created using the following commands. The databases have Oracle Managed Files (OMF) enabled and are switched to archivelog mode. For more information see: Hope this helps. Regards Tim...