I really rely on people telling me about issues they saw. And in this case, it happened twice within a few days. At OOW London, a customer came after my talk and told me about invalid objects and an incredible long recompilation time. In fact, he had to apply an OJVM patch in order to solve this. When I returned home, Jure commented on the blog about a very similar issue. I spent some time on the weekend to check it out. And I realized: There are issues with prebuilt seed databases and OJVM in 19c.… Continue reading...
It’s patching day. And I’m already downloading the patch bundles for all my installations (22.214.171.124, 126.96.36.199, 188.8.131.52, 18c and 19c). The Oracle Security Alerts for July 2019 got published today.
Patch Advisory and Risk Matrix
You can find the July 2019 Patch Advisory here. I checked the risk matrix for the database. It contains 8 new fixes for the database server. Please pay attention that 3 of the vulnerabilities may be exploitable from a client without an Oracle Database server being installed. The highest score is 9.8.
Please check the risk matrix by yourself:
- Text form of
This question came up several times in the past days: Does OJVM patching require a specific Database Release Update? People mentioned that there’s a significant difference between the OJVM Patch Readme between Oracle 12.2.01 and Oracle 18.4.0.
What’s the point?
In the OJVM (Oracle Java Virtual Machine) Patch Readme for Oracle Database 184.108.40.206 a sentence clarified that you can combine different states of OJVM and Database patch bundle with each other. Your database home could have been patched with the April 2018 Update, whereas you decided to apply the October 2018 OJVM patch.
The …Continue reading...
This is a Friday morning blog post. And actually I had no intention to write it. I don’t mean it offensive. But yesterday I received an interesting email from Frits Hoogland from Enkitec/Accenture. Frits asked me about the July RUR and some unlogic things on MOS. Once I had answered his email, the next question came in. Hence, I thought I need to write something about our July 2018 Update, Revision, BPs, PSUs – delays and other issues.
From being on stage at last year’s DOAG Conference for a “Patching Forum” I know that things aren’t as …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
Patching is fun, isn’t it? And you may have heard already that the April 2018 patch bundles got released on April 17, 2018. And I thought I share a little bit of fun with you with a quick guide to patching my databases with the April 2018 PSU, BP and RU. For this exercise I use our Hands-On Lab with Oracle 220.127.116.11, Oracle 18.104.22.168 and Oracle 22.214.171.124 installed.
Prerequisites for patching my databases with the April 2018 PSU, BP and RU
First of all, in my VBox environment, I shutdown the databases for each release before patching them – …Continue reading...
Finally … the two most important fixes for Adaptive Features are included in Oracle 126.96.36.199 October 2017 BP (Bundle Patch). I’m absolutely happy about this. Almost all of my customer and many folks outside I’m dealing with on a regular basis had to request and wait for merge patches over and over again. And we all knew – also based on the experience of the Real World Performance Team – that these two patches are so important to stabilize Oracle 188.8.131.52 production systems.
You may find this ALERT on MyOracle Support:Continue reading...
After the removal of the first Oracle Database 184.108.40.206 Bundle Patch in May, the June 2017 Proactive Bundle Patch on Linux got released now:
The Proactive Bundle Patch 220.127.116.11.170620 contains the June Database Bundle Patch and the June Grid Infrastructure Patch Set Update.
More information about previous and future BPs?
First of all, the well known schedule for BPs (and of course PSUs) will be kept – so please expect the next Proactive Bundle …Continue reading...
Can you apply Bundle Patches (BP) to Standard Edition (SE2) databases?
This question got raised by Adam (thanks!) via the comments section of the blog. But a few days later I read it on the internal mailing lists as well. Adam was referring to this sentence in the BP READMEs since October 2015:
“In this document Oracle Database Home refers to Enterprise Edition. Standard Edition Database software installs should install Database PSU.”
Why was this sentence added?
There were issues with enabling functionality on SE2 databases by accident with a Proactive Bundle Patch – something which got fixed and …Continue reading...
All credits go to Ricardo Maeda as I knew that we’ll release a Bundle Patch for Oracle 18.104.22.168 sometime this week – but I couldn’t find it linked from the usual MOS notes. And please don’t ask my why that is.
Anyhow, with patch 2579308 you’ll get access to the first BP for Oracle Database 22.214.171.124. There will be a first bigger Proactive Bundle Patch in July at the usual schedule – but this one is at least a start.
Plus in addition get the OPatch version 126.96.36.199.7 via patch 6880880.
The BP contains:… Continue reading...
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 188.8.131.52.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 …
New Parameters in Oracle Database 184.108.40.206 with July 2016 PSU/BP
By following an internal discussion and checking parameter changes between Patch Set Updates (PSU) and Proactive Bundle Patches (BP) I learned that we introduced two new SPFILE parameters in Oracle Database 220.127.116.11 with the July PSU and BP. One is documented in the patch readme, the other one can be found right now only in the Oracle Database 18.104.22.168 manual:
The Oracle 12.2 documentation about ALLOW_GROUP_ACCESS_TO_SGA, the parameter which appears not in the Oracle 12.1 documentation right now, says:
… Continue reading...
groupaccess to shared memory
At the DOAG Conference in November in Nürnberg in November 2016 a customer asked me right after my talk about “Upgrade to Oracle Database 12.2. – Live and Uncensored” why the DBA_REGISTRY_HISTORY does not get updated when he applies a Bundle Patch and follows all instructions including the “./datapatch -verbose” call.
I was wondering as well and asked him to open an SR. Which he did. And he received the message from Support that it is not supposed to appear in Oracle 12c anymore this way but only in DBA_REGISTRY_SQLPATCH. Now I dug a bit deeper …Continue reading...
Last night the July 2016 patches got released
Not all of them actually. In case you miss AIX, Intel Solaris and zLinux versions those should be available by Friday, July 22, 2016.
What’s new, what’s important?
First of all the renaming of DBIM and Exadata Bundle Patches into PROACTIVE BUNDLE PATCHES is now settled in more MOS notes.
… Continue reading...
2.1 Database patch for Engineered Systems and Database In-Memory 22.214.171.124 renamed to “Proactive Bundle Patch 126.96.36.199”
Starting from Apr2016 onwards the prior
Hurray, it’s Patching Day!
Sounds a bit like D-Day 😉 But April 19, 2016 the most recent April PSUs (Patch Set Updates) and BPs (Bundle Patches) got released.
Find all the necessary information with the below links:
The important change in the April PSU/BP release:
The database patch for “Engineered Systems and Database In-Memory 188.8.131.52” luckily got renamed into “Proactive Bundle Patch 184.108.40.206”. That is not only a rebranding but it should express that we would like to encourage you to apply the Bundle Patches…