Actually I really refused to blog about this for a few weeks now. But as I receive more questions and read more tweets, I think I need to shed some light and help avoiding confusion. And as readmes and MOS notes are not entirely in sync, you may get confused if you don’t read the “correct” document.
Oracle 19.3.0 Update (RU)
In April, Oracle released the 19.3.0 Release Update (RU) on Linux and Solaris only. As you can read in my blog post from April 25, 2019, this is a patch bundle meant for customers who installed 19.2.0 on Exadata or Solaris.
On June 5, 2019, a colleague from German ACS Support mailed me and asked if I know the reason why RU 19.3.0 has been withdrawn as he read in MOS Note: 2511334.1 (Oracle Database / Grid Infrastructure / OJVM Release Update and Release Update Revision R19 Apr 2019 Known Issues):
NOTE: A regression in DB RU 19.3.0 has been identified for updated Exadata on-premise systems. New installations of 19.3.0 are not involved.
The download of April 2019 patches that involve the DB RU 19.3.0 have been suspended.
Oracle Database Development recommends that all customers who have installed DB RU 19.3.0 or GI RU 19.3.0 instead install DB RUR 19.3.1 or GI RUR 19.3.1 respectively.
Well, I’ve had no idea. But I started to investigate.
Oracle 19.3.1 Revision (RUR)
First of all, I was a bit puzzled by the existence of 19.3.1 as an RUR. As I present about the release and patching model for quite a while now, I remember that there was no RUR planned for the initial on-prem release. In addition, an RUR should be released at quarterly intervals on the typical patch days. You can counter the first argument with “19.2.0 on Exadata was on-prem already”. And of course, it does not make sense to discuss this here. And maybe it makes more sense to release RURs as “emergency” patch bundles instead of having them on a quarterly schedule as well. But this gets decided on higher levels.
Nevertheless, my first step is to check the readme of the 19.3.1 revision:
The readme does not give you any indication about whether 19.3.1 is meant for you or not. It is a standard readme.
Only if you (hopefully) click on this link:
- Document 2511334.1 Oracle DB/GI/OJVM Update/Revision R19 Apr 2019 Known Issues
you’ll see the above text my colleague sent to me in early June. And here you will find more information:
1.1 DB RU 19.3.0 and GI RU 19.3.0 replaced with DB RUR 19.3.1 and GI RUR 19.3.1
A regression in DB RU 19.3.0 has been identified for updated Exadata on-premise systems. New installations of 19.3.0 are not involved. The download of April 2019 patches that involve the DB RU 19.3.0 have been suspended.
Oracle Database Development recommends all customers who have installed DB RU 19.3.0 or GI RU 19.3.0 to instead install DB RUR 19.3.1 Patch 29799057 or GI RUR 19.3.1 Patch 29800658, respectively. All 19.3.1 patches are available as of 4-June-2019. Please see the patch availability section of MOS Note 2498664.1.
If you ask what issue caused the withdrawal of RU 19.3.0, I can’t tell you as long as it is not mentioned in MOS Note: 2523220.1 (Database 19 Release Updates and Revisions Bugs Fixed Lists). But you won’t need 19.3.1 if you started with a standard 19.3.0 installation on any of the OS platforms. Only those you went from 19.2.0 to 19.3.0 RU will need to apply the 19.3.1 RUR. And this is also the reason why we didn’t release 19.3.1 RUR on HP-UX or AIX or zLinux. There was no 19.3.0 RU for any of these platforms. You can safely ignore the Revision 19.3.1.
And by the way, customers who downloaded RU 19.3.0 from MOS received an email alert to use now RUR 19.3.1 on top. Finally, if you are using still using 19.2.0 you can go straight to RUR 19.3.1. And once RU 19.4.0 is available, you can jump back on the RU train again.
- Oracle 19.3.0 for Linux is available for download
- Oracle 19.2.0 for Exadata is available for download
- MOS Note: 2511334.1 (Oracle Database / Grid Infrastructure / OJVM Release Update and Release Update Revision R19 Apr 2019 Known Issues)
- MOS Note: 2523220.1 (Database 19 Release Updates and Revisions Bugs Fixed Lists)
- Why Release Update Revisions (RUR) are tricky
- When you patch, use Updates, not Revisions
- MOS Note: 2498664.1 (Critical Patch Update (CPU) Program April 2019 Patch Availability Document (PAD))
- MOS Note: 2521164.1 (Database 19 Proactive Patch Information)