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...
Well, there is no Product Manager for patching. And I’m glad that I’m not in this position. But thanks to all of you, internally and externally, who share your findings with me. In this blog post I’d like to inform you about the newest patching surprises – and how to fix some of them.
Patch apply without confirmation?
Peter Lehmann informed me about this a few weeks ago. Peter told me that he patched systems with the July 2019 RU for Oracle 126.96.36.199 and recognized that the patch installed with opatch without waiting for confirmation. It looked as somebody has …Continue reading...
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 188.8.131.52. I’m patching. Can you think of anything better on a Friday night than patching?
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...
This is a Friday morning blog post. And actually I had no intention to write it. I don’t mean it offensive. But yesterday I received an interesting email from Frits Hoogland from Enkitec/Accenture. Frits asked me about the July RUR and some unlogic things on MOS. Once I had answered his email, the next question came in. Hence, I thought I need to write something about our July 2018 Update, Revision, BPs, PSUs – delays and other issues.
From being on stage at last year’s DOAG Conference for a “Patching Forum” I know that things aren’t as …Continue reading...
In this part of my blog post series about upgrading from Oracle 184.108.40.206 to Oracle 18c I’d like to demonstrate patching Oracle Database 18.1.0 to 18.2.0 on premises.
A while ago I showed also how to patch from Oracle 18.1.0 to 18.2.0 in the Oracle Cloud.
Find the related blog posts here:
- Deinstalling Oracle Database 220.127.116.11
- Installing Oracle Database 18.1.0
- Patching Oracle 18.1.0 to 18.2.0
- Upgrade Oracle 18.104.22.168 to Oracle Database 18c on-premises
Patching Oracle Database 18.1.0 to 18.2.0 on premises
Before I can start patching to the Release Update Oracle 18.2.0 I need to download the patch …Continue reading...
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
[CDB2] oracle@localhost:/u01/app/oracle/product/22.214.171.124 $ 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...
Patching is fun, isn’t it? And you may have heard already that the April 2018 patch bundles got released on April 17, 2018. And I thought I share a little bit of fun with you with a quick guide to patching my databases with the April 2018 PSU, BP and RU. For this exercise I use our Hands-On Lab with Oracle 126.96.36.199, Oracle 188.8.131.52 and Oracle 184.108.40.206 installed.
Prerequisites for patching my databases with the April 2018 PSU, BP and RU
First of all, in my VBox environment, I shutdown the databases for each release before patching them – …Continue reading...
The first RU (Release Update) for Oracle 12.2 is available on most platforms since July 18, 2017. And of course I started applying the first RU for Oracle Database 220.127.116.11 as soon as it got released.
Download the RU 18.104.22.168.170718 for Linux
First of all I downloaded the Database RU 22.214.171.124.170718 Patch 26123830 for Linux from MyOracle Support. To my absolute surprise it was very small compared to previous Proactive Bundle Patches such as the April 2017 one. It has just 40 MB in size (no typo!).… Continue reading...
I thought I won’t blog about this again:
But then a colleague of mine raised this simple question:
- “I have a customer that would like to change from patching using PSU to patching using Bundle Patch. I am
wondering what happens if my home has had several PSUs installed. Before applying a BP, would I need to rollback one by one all the PSUs that have been installed in reverse order (tedious) OR only the latest PSU (good)?”
Unfortunately the “simple” solution is hidden deep down in …Continue reading...
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
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...