opatchauto

Patching process changes with MRPs

Posted on May 22, 2023 by Patch Recommendation 10

I blogged about the Monthly Recommended Patches (MRP) several times before. And due to the feedback you and we had given, a few things got changed. The main change is from having the MRP bundled as a system patch making opatchauto a requirement. See below what Patching process changes with MRPs were implemented recently.

Before …

As you could read already in:

the introduction of the MRPs added one major flaw: They’ve been built as system patches which made …

Continue reading...

Virtual Classroom Seminar 16: Release and Patching Strategy for Oracle 19c and 23c

Posted on May 8, 2023 by Patch Recommendation Release Schedule Workshop 9

There are just two days left to sign up for our Virtual Classroom Seminar 16: Release and Patching Strategy for Oracle 19c and 23c. We’ll talk to you on Wednesday, May 10 at 16:00h CET.

What’s the topic?

We’ll try to cover everything for your best release and patching strategy with Oracle Database 19c of course, but also moving forward to Oracle Database 23c. Our big focus will be several aspects of patching. You’ll hear us talking not only about standard database patching but especially about patching in RAC environments.

We’ll put together a …

Continue reading...

MRP3 for Oracle 19.17.0 adds an interesting surprise

Posted on January 30, 2023 by Flaws and Pitfalls Patch Recommendation 9

You may have read my previous blog posts about MRPs (Monthly Recommended Patches). And today I did a quick check with Rodrigo. We both were a bit surprised to have the MRP3 for 19.17.0 add a lot of fixes to a standard RDBMS installation. So we were investigating a bit further. As a teaser, read on to see that MRP3 for Oracle 19.17.0 adds an interesting surprise.

 

How did we find out?

The MRP3 for Oracle Database 19.17.0 got released just a week ago. You can navigate to it via MOS …

Continue reading...

Binary patching is slow because of the inventory

Posted on May 10, 2022 by Patch Recommendation 52

The headline of this blog post may sound a bit cryptic: Binary patching is slow because of the inventory. But actually this seems to be one of the main causes when your binary patching gets slower and slower with every patch you apply.

The more you patch, the worse it gets

Well, this is a tough headline. But you may have read my blog posts about my quarterly patching experience. It actually started with the July 2021 RU in my 19c environment when I wrote:

At least in my environment, both checks with the

… Continue reading...

How to speed up your database and GI patching

Posted on May 9, 2022 by Patch Recommendation 12

Several of you mailed me already and commented. And I know that I promised this blog post for weeks, if not longer. So let me try to explain How to speed up your database and GI patching. Since this blog post has a longer history, I’d say far over 6 months, it will be a bit longer than the usual posts. At when I started writing it, I decided to split it up into several pieces to make it more digestible but also to allow easier finding of certain topics. I hope it may help easing some recent patching …

Continue reading...

What does datapatch do when you have different components in PDBs?

Posted on February 9, 2022 by Patch Recommendation 10

The last weeks, literally weeks, I have spent a lot of time with several patching topics. And in order to clean up my inbox a bit I will dump the learning into several blog posts. This one today will be about an interesting case I came across when a customer ran into problems with the runtime of datapatch in an ExaCC environment. Hence, today’s topic will be: What does datapatch do when you have different components in PDBs?

Annotation

If you are on 19.16.0 or higher, than you can safely ignore this blog post …

Continue reading...

Why should you use the most recent version of OPatch?

Posted on May 14, 2018 by Patch Recommendation 0

Why should you use the most recent version of OPatch?Opatch. A tool nobody really loves but everybody has to use (at least those of you who patch or aren’t in our cloud deployment). Opatch gets distributed via MOS. And you often can apply patches with an older version of OPatch. So why should you use the most recent version of OPatch?

Why should you use the most recent version of OPatch?

First of all, you have a base installation of Opatch in your $ORACLE_HOMEs:

[CDB2] oracle@localhost:/u01/app/oracle/product/12.2.0.1
$ ls OPatch
auto           jlib        opatchauto.cmd  operr.bat         scripts
config         jre         opatch.bat      operr_readme.txt  version.txt
datapatch      modules     opatch_env.sh   oplan
datapatch.bat  ocm         opatch.pl       oracle_common
docs
… Continue reading...

Grid Infrastructure PSU Jan 2015 – Am I too intolerant?

Posted on February 18, 2015 by ASM / RAC / GI Patch Recommendation 6

Germans are not only known for being precise and timely – but sometimes also for being too direct. Well, Roy could tell you stories … and I always honor his politeness 🙂

Enough about stereotypes. I work with a customer at the moment on their 12c upgrades. And I did recommend the most recent PSU (Patch Set Updates) for their Grid Infrastructure environments running Oracle Restart. Same of course for the database homes but this blog post will just name some findings I’ve had the other night when trying to apply the January 2015 GI PSU to my …

Continue reading...
Mike Dietrich
Oracle Senior Director of Product Manager for Database Upgrade, Migrations and Patching writing just another blog.

Opinions certainly are my own as is this page.

Archives

Categories

Upgrade @YouTube

Subscribe via Email

Join 7,885 other subscribers

Follow me on Twitter