Due to so many people asking me other methods besides SQLplus for provisioning PDBs; such as OEM, DBCA, etc. In this blog entry I’ll DBCA, just because its simple to show. As I mentioned in my last PDB blog,
the installer DBCA (initial DBA invocation) looks different than the subsequent (post initial db creation).
The main DBCA screen shows the following pages. We will choose Manage Pluggable Database
Choose the CDB, Note you could have many CDBs on the same Node or RAC cluster
We choose our PDB that we created in Part 1 of the blog
Ahh..we gotta open the PDB first. As before:
CDB$ROOT@YODA> alter session set container=pdbobi;
CDB$ROOT@YODA> alter pluggable database pdbobi open;
Pluggable database altered.
or CDB$ROOT@YODA> alter pluggable database all open;
Now we can Add support for and configure Database Vault. Additionally, Label Security can be configured.
It would have been nice to enable and modify Resource Manager as well other PDB tasks.
But I get the fact that this DBCA is really driven for the PDB operations (plug,unplug, create and destroy PDB).
Bulk of the PDB admin tasks are provided in EM
Let’s do a new PDB creation for grins 🙂
Specify the PDB name, storage location, and a default tablespace. Again, it would have been nice to specify a TEMP tablespace too, but that was left out
And Completion….Pretty Straightforward