Why Release Update Revisions (RUR) are tricky

A while ago we introduced Release Updates (RU) and Release Update Revisions (RUR). And despite the fact that not only we but also well known external experts such as Ludovico Caldara recommend to stay with Release Updates and simply ignore the Revisions, some people use them. There may be reasons for doing so. But in this blog post I will explain why Release Update Revisions (RUR) are tricky. Differences between Updates and Revisions? I tried to explain the differences between Updates and Revisions a while ago – and also compare them to PSUs and BPs. Differences between PSU / BP…

July 2018 Update, Revision, BP and PSU

Hurray, it’s patching day! I know, YOU did look forward to July 17, 2018 as it is patching day again. Last night we released the following Patches: July 2018 Update, Revision, BP and PSU. July 2018 Update, Revision, BP and PSU First of all, I’m doing the usual check for the alert and the risk matrix to see whether there’s are really important security patches included. For the risk matrix you’ll have to scrooooooooooolllll down quite a bit as the list of products is strictly alphabetically ordered: Critical Patch Update – July 2018 – Patch Advisory Risk Matrix for Oracle…

PSU or BP? Patch Set Update or Bundle Patch? RUR or RU?

Well, in my new role as unofficial Junior Product Manager for Patching (just kidding) I get asked once a day (at least!) via email or in customer meetings or workshops: Should we take the PSUs or the BPs? Or RUs or RURs? Addition: I updated the blog post due to the arrival of the RUs and RURs in Oracle Database 12.2.0.1.Changes are marked in orange. See. https://mikedietrichde.com/2017/07/19/first-ru-oracle-12-2-0-1-available/ Should we take the PSUs or the BPs? RURs or RUs? PSUs are Patch Set Updates, BPs are (sometimes called: Proactive) Bundle Patches. RUs are Release Upgrades which replace the BPs in Oracle…