datapatch and OPatch documentation and MOS note

Did you ever ask yourself whether there is documentation available for OPatch and for datapatch? It is not easy to find. And you won’t find it under “Database” in the Oracle Bookshelf. So today I would like to guide you in this short blog post to the datapatch and OPatch documentation and MOS note.

OPatch? Datapatch?

Just to recap: You use OPatch (or opatchauto) to apply the binaries to an Oracle installation. As a result, you change the second or the third number of the release from Oracle 19.5.0 to Oracle 19.8.0. But …

Continue reading...

Patching all my environments with the July 2020 Patch Bundles

Quarterly routine: When the new security alert get published, then it is patching time again. I’ll show you as usual how Patching all my environments with the July 2020 Patch Bundles works. And I heard your comments – in the next round in October, I will do this for GI and OJVM most likely, too. If not earlier …

And just an important annotation upfront: I patch in-place due to space issues. But in reality, you please patch always out-of-place with a separate home.

Security Alert July 2020

This is the Security Alert for

Continue reading...


Actually I carry around this topic with me since the October 2019 workshop in Dubai. We’ve had one of these OJVM Patching discussions I’d like to escape usually. Anyhow, during this session, it dawned me that the STARTUP UPGRADE requirement in the OJVM readme may be not correct anymore. So the question will be: Do you need STARTUP UPGRADE for OJVM?


Photo by Nik Shuliahin on Unsplash

A little bit of history

You will find a good amount of blog posts about OJVM here. OJVM stands for Oracle Java Virtual Machine. It is a very powerful thing and allows you …

Continue reading...

Patching all my environments with the Oct 2019 Patch Bundles

Yesterday I blogged about the Oct 2019 Patch Bundles being available for download. And while I wrote this blog post, I downloaded all of them for my environments. Here I’d like to share with you the most simple path to apply them. As I have no cluster or ASM, I don’t have to patch Grid Infrastructure. And I don’t even have OJVM in any of my databases right now. Due to space constraints in my lab environment I will apply the patches in-place. You shouldn’t do this but instead use always a new home you patch. This allows you …

Continue reading...

OPatch … oh OPatch … why is datapatch so stubborn?

Well, it is Friday night – and I’d rather should sleep or do something cool people tend to do on Friday night’s. But I try to verify a strange issue with DBMS_OPTIM_BUNDLE and the October 2018 Update for Oracle I’m patching. Can you think of anything better on a Friday night than patching?

OPatch ... oh OPatch ... why is datapatch so stubborn?

Of course I know that I’m not alone. I know at least two customers I work with right now who do some maintenance jobs tonight as well. And I’m struggling with OPatch … oh OPatch … why is datapatch so stubborn?

My test setup

I have …

Continue reading...

Do you have to execute “datapatch” when you create a new database?

Do you have to execute "datapatch" when you create a new database?Thanks to Connor McDonald (Mr. AskTom) I learned today that one topic is not clear from our patches readmes: Do you have to execute “datapatch” when you create a new database? And it’s true. It does not get explained in the readme anywhere.

Do you have to execute “datapatch” when you create a new database?

If you never applied an Oracle patch bundles you may ask now: What is “datapatch” doing. And the answer is very simple. When you apply a patch bundle usually the patch does not include only binary files but also …

Continue reading...

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 The DBCA does execute “datapatch -verboseautomatically 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.

Quick Test Scenario

I …

Continue reading...


At the DOAG Conference in November in Nürnberg in November 2016 a customer asked me right after my talk about “Upgrade to Oracle Database 12.2. – Live and Uncensored” why the DBA_REGISTRY_HISTORY does not get updated when he applies a Bundle Patch and follows all instructions including the “./datapatch -verbose” call.

I was wondering as well and asked him to open an SR. Which he did. And he received the message from Support that it is not supposed to appear in Oracle 12c anymore this way but only in DBA_REGISTRY_SQLPATCH. Now I dug a bit deeper …

Continue reading...

Oracle Database BP April16 applied successfully

Usually I don’t post twice a day but as my post scriptum for the previous blog post got longer and longer I decided to write an entry about it – maybe simply because I feel soooo happy that my patch application succeeded flawless.

For many of you the following steps may look very boring as you have done this many times. But I use the blog also to brain-dump information for myself 😉 And for those who’d like to play with it, I summarized the steps fitting exactly into our Hands-On-Lab environment.


I downloaded the following patches:

  • Database Proactive
Continue reading...

No OS Authentication? datapatch will fail in every upgrade

Thanks to Daniel from SimCorp for bringing this to my attention:Patch
Actually, command line upgrades are affected as well, if you do not use OS authentication.
Apparently, datapatch is not able to execute in non-OS authentication mode.
See MOS note 1635007.1.


You are doing a command line upgrade to Oracle Database 12c with – and you don’t use OS authentication allowing connections with “/ as sysdba” then won’t be able to execute the SPU/PSU/BP related SQL commands as it will fail to connect to your database with an ORA-1017 (invalid username/password) error.


Bug 18361221 …

Continue reading...

Don’t get puzzled by “sqlpatch” messages during Upgrade

During my last Hands-On-Labs in Uruguay and Argentina I’ve had several people wondering about these messages below when running the command line upgrade with - sqlpatch

This (and another) message breaks the nicely structured format of the output. And as it ends with an “err” extension it looks to many people as if the upgrade had gotten an error,

But please don’t feel disturbed. It’s just messages from sqlpatch invocation – and the “err” extension is just pointing to an error file in case something has gone wrong.

In a future release such messages …

Continue reading...

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