Always create databases as CUSTOM databases

I’m giving this advice to customers for many years:
When you create a fresh Oracle database ALWAYS create databases as CUSTOM databases. Via template or not doesn’t matter.

Always create CUSTOMER databasesIn the DBCA better use your own and wisely configured template rather than the prebuilt (we used to call them: seed) databases. The seed databases for “Data Warehouse” and “General Purpose or Transaction Processing” have all options and components included. I use them for testing from time to time.

As the upgrade duration mainly depends on the number of installed components I’d recommend to choose the components to install, and configure redo logs, parameters and other things wisely instead of relying on a standard which may not fit for you.

Always create databases as CUSTOM databases

First of all it is important to hit the ADVANCED CONFIGURATION button in the Database Creation Assistant (DBCA). Otherwise you will never get to the screen where you can choose between the options to install into your fresh database.

Always create databases as CUSTOM databases

DBCA- Advanced Configuration

Then you must choose CUSTOM DATABASE from the template’s section as otherwise you’ll have no control over the process.

Always create databases as CUSTOM databases

DBCA – Custom Database Template

Once you followed this guideline you’ll see the screen where you can choose which components to install into your Oracle database:

Always create databases as CUSTOM databases

DBCA – Options to install


Ideally build your own templates having exactly the options you would like to have. Use your own template to create a custom database. It takes a bit longer but it’s worth it. Don’t forget to adjust the parameters as well.

Quite often customers complain in my workshops:
Oracle has removed the screen to select the options to install” or “All options are greyed out” in Oracle 12c.

This is not really correct. First of all you’ll have to create a CUSTOM DATABASE. And second, in Oracle 12.1.0.x in case you wanted to create a Multitenant Container database the screen was greyed out indeed – but there’s a workaround for this case:

Just on the side:
This is not a recommendation to remove or delete options at no reason. But I hear this requirement and the complaints quite often and therefore wanted to clarify how to configure a database with the options you want.


Share this: