Yesterday I blogged about the Oct 2019 Patch Bundles being available for download. And while I wrote this blog post, I downloaded all of them for my environments. Here I’d like to share with you the most simple path to apply them. As I have no cluster or ASM, I don’t have to patch Grid Infrastructure. And I don’t even have OJVM in any of my databases right now. Due to space constraints in my lab environment I will apply the patches in-place. You shouldn’t do this but instead use always a new home you patch. This allows you …Continue reading...
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 …Continue reading...
There usually a philosophic battle happening when it comes to underscore parameters. The official statement is more or less: It’s an underscore, hence it is undocumented and you shouldn’t touch it unless Oracle Support advises you to do so. I agree in many cases. But in this specific one, I don’t. And in this post I will explain why you should set
_EXCLUDE_SEED_CDB_VIEW=FALSE in all your singe- and Multitenant environments. Always!
A bit of history
At first, a little bit of a history excursion. This parameter wasn’t an underscore in Oracle 12.1. You can find it as
EXCLUDE_SEED_CDB_VIEW in 22.214.171.124 …
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 …Continue reading...
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
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 126.96.36.199.Changes are marked in orange.
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 …