\nLet’s see the different ways to create a PDB, with different tools.
\nSame disclaimer here as in the first post of the series<\/a>: don’t expect to get those posts close to what you will have at the exam, but they cover important points that matches the exam topics. <\/p>\n
Documentation<\/h3>\n
Information about the exam says: Be prepared to use the non-searchable documentation during the exam, to help you with correct syntax.<\/i>
\nDocumentation about the ‘Create and manage pluggable databases’ topic is mostly in the Oracle\u00ae Database Administrator’s Guide. Search for ‘multitenant’, expand ‘Creating and Removing PDBs with SQL*Plus’<\/p>\n
You find all examples there. Remember that creating a PDB is always done from another one:<\/p>\n
- \n
- from PDB$SEED<\/li>\n
- from another PDB in your CDB<\/li>\n
- from another PDB in a remote CDB (need to create a db link)<\/li>\n
- from an unplugged PDB<\/li>\n
- from a non-CDB<\/li>\n<\/ul>\n
and the you will name your datafiles with a conversion from the original ones.<\/p>\n
Don’t forget to create the directories if you are not in OMF.<\/p>\n
SQL Developer<\/h3>\n
SQL Developer is your friend. It is designed to help you. I use it in the following way:<\/p>\n
- \n
- SQL Worksheet is a nice notepad. Even if you finally paste the statements into sqlplus, the SQL Woksheet is graphical, has colors, and can also run statements from there \ud83d\ude09<\/li>\n
- SQL Reference documentation is classified by statements. SQL Developer is classified by objects. Right clock context menu shows you what you can do on a table, on a materialized view, etc<\/li>\n
- It shows what are your options and can show you the generated SQL statement if you finally want it<\/li>\n<\/ul>\n
I’ll show you an example. You have several ways to name the files when you create a pluggable database, using the convert pairs. But if you have more than one pattern to replace, it’s not easy. Let’s use SQL Developer for that.<\/p>\n
In the DBA tab, right click on the Container Database and you have all possible actions on it:<\/p>\n
![\"Capture12COCMU-CreatePDB-000\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Capture12COCMU-CreatePDB-000.jpg\")
<\/a><\/p>\nHere are all option for the CREATE PLUGGABLE DATABASE statement. Easier that going to documentation:<\/p>\n
![\"Capture12COCMU-CreatePDB-001\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Capture12COCMU-CreatePDB-001.jpg\")
<\/a><\/p>\nAbove I’ve chosen ‘Custom Names’ to list all files. Then let’s get the SQL:<\/p>\n
![\"Capture12COCMU-CreatePDB-002\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Capture12COCMU-CreatePDB-002.jpg\")
<\/a><\/p>\nNow, I prefer to continue in the SQL Worksheet and I can paste it there. I’ve a file_name_convert pair for each files, so that I can change what I want:<\/p>\n
![\"Capture12COCMU-CreatePDB-003\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Capture12COCMU-CreatePDB-003.jpg\")
<\/a><\/p>\nSQL Developer is really a good tool.
\nWhen you unplug a PDB, it is still referenced by the original database. Then is you plug it elsewhere without renaming the files, the risk is that you drop it’s datafiles from the original container database.
\nBest recommendation is to immediately remove it from the original CDB and this is exactly what SQL Developer is doing:<\/p>\n\n
#12COCMU<\/a> Good point @OracleSQLDev<\/a>
A safe unplug must immediately remove the PDB from the original CDB pic.twitter.com\/Cdh1k7fpio<\/a><\/p>\n— Franck Pachot (@FranckPachot) November 30, 2015<\/a><\/p><\/blockquote>\n