By Mike Dietrich-Oracle on Apr 23, 2015
When Oracle Multitenant was launched Roy and I amongst many other people always mentioned that the requirement of having all options in a Container Database (CDB$ROOT), and therefore also for the PDB$SEED with the immediate result that all PDBs provisioned from the PDB$SEED will have all options as well, will hinder customer adoption significantly.
Almost all customers I have talked to in the past 3-4 years about Oracle Multitenant mentioned immediately that it will be a huge problem for them to install all options as (1) their policy is to install only things they are licensed for to (2) prevent developers, users and DBAs to use things accidentally without even knowing that this or that will require a license.
As it is not allowed to manipulate and change the PDB$SEED the workaround - as PDBs were allowed to have less options - has been to create a stand-alone Oracle 12c database with exactly the options you'd like to have configured as your gold standard - and then plug it in under a remarkable name, for instance PDB$MASTER. Switch it to read only and make sure from now on you'll provision a new PDB always as a clone from PDB$MASTER, and not from PDB$SEED.
That would have even worked in the Single Tenant case, which does not require licensing the Oracle Multitenant option and where you have only one active PDB. For this purpose you would have unplugged your PDB$MASTER after making it a pluggable database and provision new PDBs with just your desired options set as plugging in PDB$MASTER under a new name (e.g. PDB26) using the COPY option of the command.
Now this will become all obsolete as from now you it is allowed to have a CDB installation with less options. This applies to linked kernel modules (e.g. RAT) as well as to configured database components (e.g. JAVA, OWM, SPATIAL etc).
Please see the following new/rephrased MOS Notes:
- MOS Note: 2001512.1
Creating A Container Database (CDB) With A Subset Of Options
- MOS Note: 1616554.1
Customization of Database Options in a Multitenant Setup
MOS Note:2001512.1 basically explains the following steps:
- Do all the click work in DBCA (Database Creation Assistant) to create a container database - but let DBCA only create the scripts
- Edit the <SID>.sql script and remove the unwanted options according to the dependency table in the MOS Note
- Edit the CreateDBCatalog.sql in case you want to remove OWM (Oracle Workspace Manager) creation as well
- Add the Oracle PERL $ORACLE_HOME/perl/bin in front of your $PATH variable
- Start the <SID>.sh script on the shell prompt
Here's an example of a CreateDBCatalog.sql and a XXXX.sql creating a CDB with no options except XDB (which is mandatory in Oracle Database 12c):
set verify off
ACCEPT sysPassword CHAR PROMPT 'Enter new password for SYS: ' HIDE
ACCEPT systemPassword CHAR PROMPT 'Enter new password for SYSTEM: ' HIDE
host /u01/app/oracle/product/188.8.131.52/bin/orapwd file=/u01/app/oracle/product/184.108.40.206/dbs/orapwXXXX force=y format=12
This results in a database having only these components - the minimal component set in Oracle 220.127.116.11:
COMP ID NAME
CATALOG Oracle Database Catalog View
CATPROC Oracle Database Packages and
XDB Oracle XML Database