Creating CDBs and non-CDBs with less options

I wanted to write up this blog post a long time ago. When Helen Vanderheide did ask me a few weeks ago if she can omit catoctk.sql during the creation of the database, I realized that I should update my previous blog posts about Creating CDBs and non-CDBs with less options. And of course, the following is usable with non-CDBs as well. You’ll find an example and especially the component dependency matrix below as well as many links to related blog posts at the end. If you don’t want to read all this, just scroll down to the Summary. Why…

Do you have to execute catbundle.sql when you create a new 11g database?

Roberto Valsania asked this question once he read my blog post about whether you have to execute datapatch after creating a new 12c database: Do you have to execute catbundle.sql when you create a new 11g database? I’d bet you all are aware that Oracle Database 11.2.0.4 will go out of Waived Extended Support by end of 2018. But that doesn’t answer the question. So I did a quick experiment and created a fresh 11.2.0.4 database to answer the question. Do you have to execute catbundle.sql when you create a new 11g database? First of all, let me clarify what…

Create Multitenant databases with DBCA – Things to Know

When you create Multitenant databases with DBCA there are some Things to Know. And in Oracle Database 12.2.0.1’s Database Creation Assistant (DBCA) there is a common pitfall in the “Options” screen. It was grayed out in the previous release but when you choose to create a “custom” database you can select the options/components now. Be careful … Previous posts I did blog several times about the DBCA already: Always create databases as customer databases Use your own templates in DBCA when you create databases Does DBCA execute datapatch in Oracle Database 12.2? Create Container databases with less options And there…

Use your own templates in DBCA to create databases

Another advice regarding database creation: Use your own templates in DBCA to create databases. This way you can configure not only the options and components to create but also redo log layout, your set of parameters and much more. And it is less error prone than a “create database” script. Use your own template in DBCA Creating your own template in DBCA (Database Configuration Assistant) is quite easy and straight forward. In DBCA select “Manage Templates”: and create a new template: from an existing database template: Choose the “Custom Database” template as blueprint: Choose the components you’d like to have…

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. In 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…

Does DBCA execute “datapatch” in Oracle 12.2?

Does the Database Configuration Assistant (DBCA) execute “datapatch -verbose” in Oracle 12.2 when you create a new database? Does DBCA in Oracle 12.2 execute datapatch when you create new database? I was curious if this misbehavior from the previous release has been fixed. Good news: It got fixed with Oracle Database 12.2.0.1. The DBCA does execute “datapatch -verbose” automatically now when you create a new database. In the previous release this did not happen – you had to execute it manually after creating a new database. DBCA 12c and “datapatch.pl” – things to know Quick Test Scenario I applied the…

Create a database with NON-DEFAULT Time Zone

One requirement of Transportable Tablespaces (and of course Full Transportable Export/Import as well) is to have identical database character sets AND identical time zone settings. Problem Source database has a lower time zone setting than the default target database in the destination home. Lets assume you’d like to migrate an Oracle 11.2.0.4 off IBM AIX and migrate it into Oracle 12.1.0.2 on an Exadata meaning Oracle Linux 6. The source time zone version if it has never been upgraded would be TZ V14 – whereas the new Oracle 12.1.0.2 database you’d create would get TZ V18 by default. Solution 1…

DBCA 12c and “datapatch.pl” – things to know

A few weeks ago I did blog about the DBUA (Database Upgrade Assistant) not executing ‘datapatch’ (i.e. not applying the SQL changes involved with a SPU/PSU/BP) automatically: DBUA 12c and “datapatch.pl” – things to know For DBUA, please note that this behavior DOES NOT APPLY to command line upgrades done with catctl.pl – as you can see from this somewhat disturbing messages¬†during the upgrade in phase 65 and phase 69¬†(which are not errors but just informational messages for datapatch’s execution): But afterwards I have learned that things are worse. The same behavior is true when you create a database. Not…