DBCA 12c and “” – 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:

For DBUA, please note that this behavior DOES NOT APPLY to command line upgrades done with – 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):

Datapatch phases command line upgrade

But afterwards I have learned that things are worse.
The same behavior is true when you create

Continue reading...

Grid Infrastructure Management Repository (GIMR) – Datapatch?

I have blogged about the Grid Infrastructure Management Repository (GIMR) a while back:

And Markus Michalewicz, our Director of Product Management, Oracle Real Application Clusters (RAC), has published a very interesting and helpful insight article about GIMR on July 30, 2015. Read it here:

Since Oracle Database the GIMR database will be created by default – and it is a single tenant database having a CDB$ROOT and one active PDB.

Recently the question came up if – in the likely event of applying a PSU …

Continue reading...

PSU1 and PSU2: Datapatch Issues coverd in MOS Note

You may have read a posting dis-recommending PSU1 and PSU2 for Oracle Multitenant especially in RAC/GI environments earlier this week. Actually following a lot of internal discussions I will post some advice and clarification later this week.

Now I have an useful update:
Datapatch Issues are covered within a separate MOS Note making it easier to keep track and find workarounds for known issues.
Please see MOS Note:1609718.1 Datapatch Known Issues


Continue reading...