We can use the Oracle CREATE PLUGGABLE DATABASE command to manually clone a pluggable database. Pluggable Database Clone Connect to container database $ sqlplus / as sysdba Show connection Name SQL> SHOW CON_NAMEĬDB$ROOT Show status of pluggable databases SQL> SHOW PDBSĤ PDB1 READ WRITE NO Create Pluggable Database (pdb2) If you’re interested and what to have a look at the above scripts I have shared the example cloning scripts here.
Target clone database ‘pstb’ on z-oracle2 Let’s start by cloning our source Oracle ASM database to our test server, and repeat the same size check. Source database ‘psta’ on z-oracle1 Non-Production Clone In the post I will clone my source database to my target database server using a Protection Group storage snapshot, and then then create pluggable database ‘PDB2’ from ‘PDB1’ in the target database using the Oracle ‘CREATE PLUGGABLE DATABASE’ command. The image below shows my lab layout of a source database server running an Oracle database with a single pluggable database ‘PDB1’, and a target database server to host our cloned database and PDBs. In this Blog I am going to show how we can also create a space efficient Pluggable database (PDB) clone using a modern all-flash storage array on Oracle ASM using the ‘CREATE PLUGGABLE DATABASE’ command.
You can read-up on how to use Snapshot Copy, Oracle dNFS and a FlashBlade to clone pluggable database here. With the above, and the announcement of de-support of non-CDB architecture from 20c I produced a blog on how to use the SNAPSHOT COPYoption to create space efficient database clones with dNFS.
One of the most exciting announcements at last years Oracle Open World #OOW19 was around multi-tenancy and the changes to Oracle licensing allowing non multi-tenant users to have up to 3 user-created PDB’s in a container database at any time for free.