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...
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...
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...
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 22.214.171.124, 126.96.36.199 or 18c below a certain patch level, the CSSD demon fails to …Continue reading...
I need to bring this blog post forward about AutoUpgrade and Data Guard, RAC, Restart and non-CDB to PDB. Initially I planned to write this a bit later. But some of you had questions or were wondering why AutoUpgrade hasn’t done certain tasks. Hence, I’d like to clarify what AutoUpgrade can do, what it can’t and what you’ll have to do at the moment.
I refer to the AutoUpgrade tool as of July 2019. In later versions, one or the other restriction may be lifted. I will blog about it then as well.
AutoUpgrade – Step-by-stepContinue reading...
This blog post title sounds a bit weird, doesn’t it? Oracle 188.8.131.52 RESTART: Make sure you’ve patched your Oracle 184.108.40.206 homes. Why the heck should you patch your 220.127.116.11 database homes upfront?
Oracle 18.104.22.168 RESTART: Make sure you’ve patched your Oracle 22.214.171.124 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...
During the installation of Oracle Grid Infrastructure 126.96.36.199 you’ve had the an option to choose YES/NO to install the Grid Infrastructure Management Repository (GIMR) database MGMTDB – but as of Oracle 188.8.131.52 Grid Infrastructure Management Repository (GIMR) database now mandatory in Oracle GI 184.108.40.206:
GIMR database now mandatory in Oracle GI 220.127.116.11
With Oracle Grid Infrastructure 18.104.22.168 this choice has become obsolete and the above screen does not appear anymore. The GIMR database has become mandatory.
What do we stored in the GIMR?
- You’ll find it in the Oracle 22.214.171.124 documentation via this link.
In addition please see the …Continue reading...