Uwe Kirchhoff, one of the best techies I know in the entire Oracle CSS (formerly ACS) Support, mailed me before the Christmas holidays with a simple question. He discovered that altering init.ora parameters in a session does not necessarily write the parameter down into the spfile. Sounds a bit like Voodoo with init parameters, and Oracle Restart has a role in this story as well. If you don’t have or do not plan to use Oracle Restart, then this is not interesting for you. But of course, you are free to still read it 🙂… Continue reading...
One and a half weeks ago we released the Database and Grid Infrastructure Release Updates (RU) 19.18.0. You could read on the blog how to apply it, and you could read also about an alert. So far, all was more or less transparent but apparently sort of an Hide and Seek with RU 19.18.0 has happened. So let me shed some light.
I am just the messenger trying to bring some light into the topic. Neither is our team responsible nor do we have any sort of control on this process. I …Continue reading...
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...
Funny, I was traveling recently with RAC PM Anil Nair – but he forgot to tell me that this cool story has been published just a few days before we took of for YATRA 2022 to India: Intel uses AutoUpgrade to upgrade from Oracle 126.96.36.199 to 19c. I know that Anil is simply so busy – and my surprise was huge.
What’s the story?
Gagan Singh, Enterprise Architect at Intel, shared it with me last week. The goal was to upgrade from Oracle 188.8.131.52 to Oracle 19c with the least amount of downtime …Continue reading...
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:
… Continue reading...
At least in my environment, both checks with the
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 184.108.40.206 – End of Support and Patch Bundles.
Premier Support for Oracle 220.127.116.11
If you remember this, the Premier Support period for Oracle 18.104.22.168 ended on November 30, 2020.
Limited Error Correction Support for Oracle 22.214.171.124
Since many of you were still on Oracle 126.96.36.199 when the end of Premier Support …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...
No worries, this isn’t a blog post from the vault. And I haven’t accidentally published something from the past just today. It is real. Oracle Database 188.8.131.52 and GI are certified on OL8 and RHEL8.
What has been certified?
Thanks to my colleagues and a large customer in the UK, I received an email asking whether I have seen this information already on MOS. I haven’t. I knew that there were discussions but I had no actual date for the 184.108.40.206 certification on OL8 on my radar.
So in brief, these Linux 8 releases …Continue reading...
This will be a very short blog post today. But a colleague asked me this question just a few minutes ago: Which database version can be used with Grid Infrastructure 19c? And I realized that I neither put it on the blog yet nor did I bookmark it. But I answered this question several times already.
Which database version can be used with Grid Infrastructure 19c?
There are 4 sources I did check:
- MOS Notes on MyOracle Support
- Oracle Documentation
- Certification Information on MyOracle Support
- Database Upgrade Blog
At first, I answered with MOS …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 220.127.116.11 GI installation corrupted the inventory. Hence, there seems to be some …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
This blog lives a lot from customer’s feedback and updates. And these days, Nicolas Jardot from dbi-services in Switzerland sent me an email asking: Where does the database link SYS_HUB come from? And if he can delete it or if it has any deeper purpose. Neither Google nor MOS reveal a lot of useful information
Where does the database link SYS_HUB come from?
I took my vanilla 18.3.0 database in our hands-on lab and check:
column owner format a5 column db_link format a12 column username format a12 column host format a12 select con_id, owner, db_link, username, host from cdb_db_links; CON_ID… Continue reading...
This blog post title sounds a bit weird, doesn’t it? Oracle 18.104.22.168 RESTART: Make sure you’ve patched your Oracle 22.214.171.124 homes. Why the heck should you patch your 126.96.36.199 database homes upfront?
Oracle 188.8.131.52 RESTART: Make sure you’ve patched your Oracle 184.108.40.206 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...