opatchauto

Binary patching is slow because of the inventory

Posted on May 10, 2022 by Patch Recommendation 23

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 4

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 8

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?

Different components?

In a Multitenant environment you can choose various strategies for database components. When you …

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

Archives

Categories

Upcoming Events

There are no upcoming events at this time.

Upgrade @YouTube

Subscribe via Email

Join 6,000 other subscribers

Follow me on Twitter