It took a while – but now you can find a new MyOracle Support (MOS) Note with a list of Important Recommended Patches for Oracle Database 19c. It is actually a must-read, regardless whether you are upgrading or migration to 19c, or in case you are already on 19c.
What do you get?
Please check MOS Note: 2720807.1 – Oracle Database 19c Important Recommended One-off Patches. It gives you a list of important fixes for Oracle Database 19c. In the initial version of the note you could select for each available Release Update (RU) since 19.4.0. This has now been changed because you shouldn’t be on 19.4.0 or 19.6.0 anymore. The note will contain the information for the past 4 RUs. This covers one year – and we are pretty certain that this should be fine.
When you access the note, you find a strange title (ignore that) but also – very important – a check box list on top:
Following a recent Twitter discussion I’d like to clarify that I’d like to explain that the sole idea of this note is to give you heads-up, especially when you are on an older RU about known issues. Ideally all of the listed issues get fixed in future RUs wherever possible. This is obviously the case when you click on 19.7 at first, then on 19.8. and so on. The list gets smaller and smaller. Simple reason: a lot of the issues we saw in 19.7. and 19.8 are fixed already in 19.10.0.
For instance, when you tick 19.7.0 at the moment while I write this you will get a list of 25 important one-off patches on top of 19.7.0:
And when you hit now the 19.10 filter option, you get a list of only 6 issues at the moment:
What you don’t get!
You won’t get a full list of existing issues. Let’s say, you are on 19.8.0 and you click the 19.8.0 filter button, then you won’t see all existing issues with 19.8.0. You will only get a list of IMPORTANT one-off fixes on top of 19.8.0. This is a curated and selected list based on the information our Sustaining Engineering team compiled together with Support. Markers such as “how often has an issue happened and been tagged with SRs” and “how critical is an issue” are the basis for the list. And of course also the availability of a one-off fix.
Do you have to install all of them?
Good question – and I’d say “No!”.
But you should browse through this list on a regular basis. This is why you should add this to your favorite notes. You can simply do this by clicking on the grey star in the upper left corner of the note – in my above screenshot it is yellow as I added it already. Afterwards you can easily navigate to it via the favorites bookmarks in MOS left of the SEARCH field:
This makes it much easier to find the note again.
Check it once per month ideally.
And I guess I don’t need to tell you that you should apply 19.10.0 RU.
Further Links and Information
- MOS Note: 2720807.1 – Oracle Database 19c Important Recommended One-off Patches
- Patching all my environments with the January 2021 Bundle Patches
If these one-off patches have been marked as Important Recommended. What is the reason for not including them in the latest RU’s?
e.g. 32245850 is listed for all RU’s from 19.7 to 19.10. Why not just include in the RU itself?
there can be many reasons. For instance, the issue has been detected and fixed just recently, and hence didn’t match the code freeze date for 19.10.0.
Or the fix can’t be included in an RU as it is not “RAC rolling”. Or it just became clear that this is really something which hit more customers. As usually it takes a few weeks until an RU gets consumed more widely, it may take also a bit until we can detect an issues as significant.
But our goal is to include all of them in a future RU.
Just something I noticed. Better click the grey star close to the title of the document instead of clicking on the favorite star you mentionned 🙂 It works better !
Have a great day 🙂
What I would love to see added to this…
DBA_REGISTRY and spfile cross-references.
When I find feature specific issues it can often be tracked back to ‘defaults’ or first use of something in the database.
what do you mean with SPFILE cross-references?
Regarding features, unfortunately I can’t always be tracked back. And there may be side effects which are visible in the bug but not obvious to the reader.
I see your point, but I doubt that we’ll have a chance to get this added.
I am trying to download scripts Sql script repository, but unable to download it because of permission issue.
Kindly allow me to download it.
sorry for the inconvenience – this is broken right now due to API changes on the blog.
I will move the scripts to GIT asap.
Sorry for the inconvenience …
when script will.be available for download, really helpful for all.of us.
Ah, got you – I will make them available ASAP.
Sorry for the inconvenience.
When it will be available for download, this is very helpful for us.
the links to download the one-off patches are in the MOS note.
If we apply 19.10 RU plus some of the recommended “one off”, when we want to apply some higher RU (19.11 , 19.12…) is necessary rollback the “one off” before?
the opatch check will tell you when you run it with 19.11.0.
It will tell you the conflicts, and then you should request these via an SR.
You don’t have to rollback them – the 19.11.0 RU will wipe them out.
Hi Mike, strange patches are listed here for 19.11 version. E.g. patch 32259535 was added on 24/Feb/21; so before 19.11 got released. And when I select “list patches” there is NO patch for version 19.11. So my question is: did the list get corrupted in any way? Thanks Peter
yes, there were several issues with this note unfortunately.
But it is supposed to be fixed now.
Unfortunately document “MOS Note: 2720807.1 – Oracle Database 19c Important Recommended One-off Patches” is not available anymore as it can’t be found anymore on Metalink :-(. Hopefully it will be back online again soon.
It’s available again… However it seems they have changed the contents/layout of the document a little bit.
MOS has a terrible mechanism – whenever somebody updates the note, it goes automatically into REVIEW state – and another person has to review it and publish it again. During this period, the note is not visible externally. And even worse, for you as a customer there is no sign that such a thing will happen.