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...
This will be a short blog post but since I received a number of messages yesterday after I published my usual Patching all my environments with the April 2022 Patch Bundles blog post I need to clarify a few things regarding Oracle Database 220.127.116.11 – End of Support and Patch Bundles.
Premier Support for Oracle 18.104.22.168
If you remember this, the Premier Support period for Oracle 22.214.171.124 ended on November 30, 2020.
Limited Error Correction Support for Oracle 126.96.36.199
Since many of you were still on Oracle 188.8.131.52 when the end of Premier Support …Continue reading...
Actually I planned for a different blog post this morning. But since I have a backlog of unanswered comments accumulated I came across this interesting question from Pedro. He wanted to know how he can patch the OCW component in his database home. So I thought I will show you the process of Adding the Oracle 19.14.0 OCW / GI bundle patch to my database home.
Is this necessary?
That’s a good question for a Monday morning. I think: No, that isn’t necessary for a “Database only” home where you don’t have or …Continue reading...
You may have read my previous blog post about patching all my environments to the January 2022 patch bundles. But since I do this in a very simple non-RAC, non-GI environment, I may not see issues you may have encountered. Some people commented – and I would like to share Some additional information regarding the Oracle 19.14.0 RUs . Still, please, this is NOT a collection of all open issues. I just see this blog post as a summary of the issues I have seen and/or heard about so far.
555.1 is one… Continue reading...
This is the right blog post for a Friday 13th. And please forgive me – I wanted to put this on the blog earlier as two of my customers hit this weeks ago already. But it must have fallen through the cracks. Still, now it is hopefully not too late to tell you what you should do if you hit ORA-29702 – and your instance does not startup in the cluster anymore. Especially when you tested a database upgrade – and after a restore, the database doesn’t want to start, no matter what you try.… Continue reading...
A long while ago I blogged about whether you should keep your patch versions between Grid Infrastructure and Databases Homes in synch, or not. And today, Daniel dropped me a note mentioning that this old blog post may need an update for 18c/19c. He’s right. And as I’ve had trouble finding my old blog post, I title this one a bit more obvious: Does your GI RU/RUR patch level has to match your database’s?
Before Oracle Database 18c
Since Oracle 18c we move from a 5-number release schema to a 3-number one. …Continue reading...
To be very honest, when I posted a few days ago, Oracle Database 19c is certified on OL8/RHEL8 I didn’t check for the Oracle Clusterware (OCW) certification. I blindly assumed that this is the case. But from comments and discussions on twitter, I realized it may be necessary to point this out explicitly to avoid confusion. Even though my fellow mate, RAC Product Manager Anil Nair has pointed it out already many times: Of course, Oracle Clusterware is certified on OL8/RHEL8 as well.
Find it on MOS
Your source for certification information …Continue reading...
Thanks to all our customers who participated in our evaluation test for RAC upgrade support with the AutoUpgrade Tool. And my colleagues worked hard to deliver the new version as quickly as possible. Just to make sure: This is not an April’s fools blog post. Since 2 days, you can download AutoUpgrade – New Version with RAC Database Upgrade Support.
Where to download it?
As usual, you can download the newest version – in this case 19.8 aka 20200327 from MOS Note: 2485457.1:
You simply copy the new version into your 19c (or …Continue reading...
From time to time, when I discuss OJVM patching with customers, I hear the following question: Do you need to apply OJVM patches to Grid Infrastructure? I’m carrying around this topic since months actually.
A quick MOS check
Well, you’d assume this is something MOS does give you an answer within fractions of a second. But nope. I found a lot but unfortunately not what I was looking for. What I found instead where community discussions where applying OJVM patches to a 184.108.40.206 GI installation corrupted the inventory. Hence, there seems to be some …Continue reading...
Thanks to my colleague Sebastian Alasino who works in the MAA team out of the UK. Sebas highlighted this issue to. And I’d like to share it with you when you attempt to upgrade Grid Infrastructure to Oracle 19c. If you have the Docker RPM installed and you were lazy on patching, then GI Patch 28553832 may be needed before you upgrade to 19c.
What is the issue?
If the Docker Engine RPM is installed and your GI version is 220.127.116.11, 18.104.22.168 or 18c below a certain patch level, the CSSD demon fails to …Continue reading...
This is just a short blog post to ensure I will find the necessary information when somebody asks me again.. In case you plan to do an Exadata upgrade to OL7 and to Oracle 19c, the below links are the most important ones you should start with.
- Exadata Database Machine – Maintenance Guide: Updating Exadata Software
- Upgrade to Oracle 19c on Exadata with AutoUpgrade
- MOS Note: 2542082.1 – 19c Grid Infrastructure and Database Upgrade steps for Exadata Database Machine running on Oracle Linux
- Fred Denis’ “An Unknown DBA” Blog with lots of tips and tricks and more
Interesting things happen. And I learned (credits to Arun Gupta and others) that there is a change in Oracle Database 12.2 environments I wasn’t aware: The DBCA 12.2 does not update
/etc/oratab in GI / RAC environments. Let me give you some extra information and hints on this topic as it may cause some strange situations.
DBCA 12.2 does not update /etc/oratab in GI / RAC
Arun Gupta commented on the blog:
… Continue reading...
Another case in point. DBCA fails to update the /etc/oratab file in 12.2 when a database is created. There is no documentation of this behavior. So, I opened
This blog post title sounds a bit weird, doesn’t it? Oracle 22.214.171.124 RESTART: Make sure you’ve patched your Oracle 126.96.36.199 homes. Why the heck should you patch your 188.8.131.52 database homes upfront?
Oracle 184.108.40.206 RESTART: Make sure you’ve patched your Oracle 220.127.116.11 homes
Well, there’s an interesting issue happening. When you work with Oracle Grid Infrastructure, no matter if you operate a cluster or “just” use Oracle Restart, you’ll have to upgrade GI to Oracle 12.2 first before you can manage 12.2 databases with it. That’s not new. It’s a well understood rule.
Now guess you operate Oracle RESTART (SIHA …Continue reading...
I’ve had some interesting discussions with Anil Nair, our RAC Product Manager and a customer in the past days. The customer was looking for a definite statement that they can have a higher version of Patch Set Updates (PSUs) or Proactive Bundle Patches (BPs) in the Database homes than in the Grid Infrastructure home managing the resources.
For Oracle Database 18c, 19c and onward, please read instead:
Can you have different PSU/BP versions between Database and GI homes?
Yes, you can have a higher version PSU …Continue reading...
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...
You may have read a posting dis-recommending PSU1 and PSU2 for Oracle Multitenant 18.104.22.168 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
Just received this question from a colleague these days:
“The current customer environment is 10.2.0.5 on Linux with a 2 node RAC cluster having OCR and Voting Disks on RAW devices. Customer is concerned about the possibility of upgrading to 11gR2 Grid infrastructure first before they could upgrade to 12c Grid
Now the answer is written down in MOS Note 1572925.1:
How to Upgrade to 12c Grid Infrastructure if OCR or Voting File is on Raw/Block Devices
Basically the MOS Note says:
You will have to relocate your OCR/Voting to a supported device BEFORE you can upgrade …
A few weeks ago I’Ve posted something about the deinstall utility as OUI doesn’t offer a “deinstall software” option anymore:
How to deinstall “old” SW after 22.214.171.124 has been applied?
And I’ve got some feedback (which is a good sign as it means that some of the content might be useful and will be read – and from the follow-up you see that we’ll read your comments and emails as well 🙂 ).
Anyway, the feedback was either CRS deinstall does not work the right way or deinstall cleans up too many things. So Roy did follow …Continue reading...