Database Reference
In-Depth Information
SQL> create user common_user identified by common_user container=all;
create user common_user identified by common_user container=all
*
ERROR at line 1:
ORA-65096: invalid common user or role name
SQL> alter session set "_ORACLE_SCRIPT"=true;
Session altered.
SQL> create user common_user identified by common_user container=all;
create user common_user identified by SEcret__123 container=all
User created.
SQL> alter session set "_ORACLE_SCRIPT"=false;
Session altered.
But the above is not officially supported, so it's probably best to avoid it.
It is very important to know that the CDB must have all the options of all its PDBs, and thus the CDB is created
with all options enabled just in case. This does not affect licensing as the CDB does not contain data, but it does mean
that
pdb$seed
also has all options enabled, and thus all PDBs created from the seed will have all options enabled,
which does have a significant licensing impact. So create a separate PDB “master” with the options you require and
use that for creating new PDBs—not the
pdb$seed
.
This is how to create another pluggable DB from a PDB “master:”
create pluggable database pdb1 from pdb_master;
Remote cloning will be possible on release two:
create pluggable database pdb1 from pdb_master@myserver;
As a general tip, try to consolidate DBs with similar downtime requirements as they will tend to be brought up
and down together from the host CDB. Resource manager is an important method to control contention between
PDBs. You can limit CPU per PDB but can't do memory limits per PDB as yet. It is well worth putting your 12c redo
logs on fast disks as the log writer is likely to become a bottleneck.
After upgrade and plugin, check
pdb_plug_in_violations
for error messages.
That is the end of the pluggable DB primer chapter. For more detail on 12c in general, I would obviously have a
look at Oracle's documentation and also consider purchase of
Expert Consolidation in Oracle Database 12c
by Martin
