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...
As of Oct 15, 2019, the CPU October 2019 Patch Bundles are available for download. So let me do the quarterly exercise to download and install all of them into my various environments.
Critical Patch Alert October 2019
At first, I check the Alert and the Risk Matrix whether critical issues with a high risk score are included. I will install the patch bundles anyway, but I’m curious. In my particular case I will take care on the database only. You of course will check for other products you are using, too.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...
As usual I download the patch bundles and apply them to our Hands-On Lab environment as quickly as possible. First of all for the simple reason that I don’t want to trap into issues which are fixed already. Second for the reason that I always tell you: YOU MUST PATCH! But if I’m saying this over and over again, then I can’t have my own environments unpatched. And at third, because I want to learn if anything is not working correctly or has changed (see below).
Of course my tiny single instance environments are not comparable to your critical production …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
The last Office Hours I’ve run about the New Release and Patching Model didn’t go very well technically. I’ve had screen/display issues. And Steven Feuerstein tried to save the best parts – but despite Steven’s awesome work neither him nor I did really like the result. So I decided that it may be better to record a Video: The New Database Release and Patching Model again (which I actually planned for quite a while already anyway.
Video: The New Database Release and Patching Model
The video is based on the slide deck you’ll find in the Slides download section of …Continue reading...
Roberto Valsania asked this question once he read my blog post about whether you have to execute
datapatch after creating a new 12c database: Do you have to execute
catbundle.sql when you create a new 11g database?
I’d bet you all are aware that Oracle Database 220.127.116.11 will go out of Waived Extended Support by end of 2018. But that doesn’t answer the question. So I did a quick experiment and created a fresh 18.104.22.168 database to answer the question.
Do you have to execute catbundle.sql when you create a new 11g database?
First of all, let me clarify …Continue reading...
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 22.214.171.124, Oracle 126.96.36.199 and Oracle 188.8.131.52 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...
Thanks to Connor McDonald (Mr. AskTom) I learned today that one topic is not clear from our patches
readmes: Do you have to execute “
datapatch” when you create a new database? And it’s true. It does not get explained in the readme anywhere.
Do you have to execute “datapatch” when you create a new database?
If you never applied an Oracle patch bundles you may ask now: What is “
datapatch” doing. And the answer is very simple. When you apply a patch bundle usually the patch does not include only binary files but also …
Since Oracle Database 184.108.40.206 we change our patching model as well, switching from Patch Set Updates (PSU) and Proactive Bundle Patches (BP) to Release Updates (RU) and Release Update Revisions (RUR). But what are actually the differences between PSU / BP and RU / RUR patch bundles? Is there any or is it just a renaming of well known patch bundles?
No change on MS Windows
First of all, let me say that there won’t be any changes on the Windows platform. If your preferred operating system is MS Windows then stop reading here. On Windows you’ll see …Continue reading...
It’s October 17, 2017. And the October 2017 RU, RUR, BP and PSU are available for download.
The most important links
Find the most important information here:
- Landing page for Security Alerts and Third Party Bulletins
- Critical Patch Update – October 2017
- Oracle Database Server, versions 220.127.116.11, 18.104.22.168, 22.214.171.124
The Risk Matrix
Database RU, RUR, BP and PSU – October 2017
To access the RU, RUR, BP and PSU for the Oracle Database Server you will have to logon to MyOracle Support:Continue reading...
How often did I launch a search in MyOracle Support (MOS) for a specific Bundle Patch or Patch Set Update. And usually the MOS search results don’t get me what I’m looking for no matter how clever I search. But there was relief. A MOS Note combined all PSUs and BPs and much more into table format including the links. But what if there would be a Download Assistant for RUs, RURs, BPs, PSUs, Patch Sets and Releases?
I did blog about the previous magic note a while back:
Where is the Jan 2017 PSU for Oracle Database 126.96.36.199?…
That’s an interesting question a customer raised the other day:
How to patch the Oracle Instant Client?
I silently assumed that there’s a new release of the Oracle Instant Client every quarter or at least when we deliver fixes which apply to the client as well. Hm …
What is the Oracle Instant Client?
First of all, the Oracle Instant Client is a pretty cool thing. It gets distributed via OTN as a simple download. You deploy it to your client machine, you set LD_LIBRARY_PATH (or PATH on Windows) and add a tnsnames file if necessary, you may add SQL*Plus …Continue reading...
The first RU (Release Update) for Oracle Database 188.8.131.52 has been released. And Oracle Support provides some very helpful documents to explain the implication of the new RU (Release Update) and RUR (Release Update Revision) patches.
More Information about RU and RUR patches for Oracle 12.2
First of all, these are the most important MOS notes to have a look at:
- MOS Note:742060.1 – Release Schedule for Current Database Releases (updated Aug 3, 2017 )
- MOS Note: 2285040.1 – Release Update and Release Update Revisions for Database Proactive Patch Program
- MOS Note: 2275525.1 – FAQ for RU and RUR (not
The first RU (Release Update) for Oracle 184.108.40.206 is available
Just in case the port you are looking for is not available right now please see the ETA dates in the link below.
Details of the July 2017 Critical Patch Advisory
Find the General Information about the July 2017 Critical Patch Advisory here:
Find the Risk Matrix for the July 2017 Critical Patch Advisory here:
The details about the Database are included in this document:
MOS Note: 2261562.1 – Patch Set Update and Critical Patch Update July 2017 Availability Document
Please find the “Missing patches” in section 2.2 …
After the removal of the first Oracle Database 220.127.116.11 Bundle Patch in May, the June 2017 Proactive Bundle Patch on Linux got released now:
The Proactive Bundle Patch 18.104.22.168.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...
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 22.214.171.124.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 …
I’ve had some interesting discussions with Anil Nair, our RAC Product Manager and a customer in the past days. The customer was looking for a definite statement that they can have a higher version of Patch Set Updates (PSUs) or Proactive Bundle Patches (BPs) in the Database homes than in the Grid Infrastructure home managing the resources.
Can you have different PSU/BP versions between Database and GI homes?
Yes, you can have a higher version PSU or BP in the Database home than in the Grid Infrastructure home managing the resources. This is implicitly documented in MOS Note 337737.1 – …Continue reading...
Thanks to Murthy who commented on this blog post and Jeannette Holland (SimCorp) who opened an SR resulting in an ER.
DBMS_QOPATCH in Multitenant
DBMS_QOPATCH will deliver useful information about installed patches only when executed within the CDB$ROOT. It has been designed this way for security reasons in Oracle Database 12.1 but I can easily see a need to check for installed patches within a PDB as well.
I “borrowed” this test case from Jeannette’s SR:
… Continue reading...SQL> COLUMN NAME FORMAT A8 SQL> SELECT NAME, CON_ID, DBID, CON_UID, GUID FROM V$CONTAINERS ORDER BY CON_ID; NAME CON_ID DBID CON_UID GUID --------
New Parameters in Oracle Database 126.96.36.199 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 188.8.131.52 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 184.108.40.206 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
Where is it?
This question reached me a week ago:
“Where is the January 2017 PSU for Oracle Database 220.127.116.11?”
“What’s the deal?” was my first thought – just go and download it from MOS.
Well, not really …
Where to download Proactive Bundle Patches, Patch Set Updates and Patch Sets?
My favorite note is:
Quick Reference to Patch Numbers for PSU, SPU(CPU), BPs and Patchsets
It gives me access to all the download links for the patch bundles I’m looking for.
But for 18.104.22.168. there’s only “NA” (not available) stated:
And a very …Continue reading...
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...
Just received a message from Oracle Support this early morning as I did install the Proactive Bundle Patch from October 2016 into my Oracle Database 22.214.171.124 environment saying:
Dear Oracle Customer,
You are receiving this email because our recordsindicate you downloaded the following patch:
Patch number: 24448103
Release: DB Proactive Bundle 126.96.36.199.161018
Platform: Linux x86-64
This patch has been replaced and is now available for download. Please review section 1.1 of the
following My Oracle Support note for further technical details and instructions:
Note: 2171506.1 – Oracle Database Proactive Patch 188.8.131.52.161018 Known Issues
… Continue reading...
SCAN Listener or local listener
What will you get when you download the most recent Oracle Database PSU or BP from October 2016?
MOS Note: 1683799.1 – 184.108.40.206 Patch Set – Availability and Known Issues is not entirely clear. Therefore lets shed some light …
This matrix in MOS Note: 1683799.1 tells you about the availability of PSUs and BPs for a regular database installation (non-RAC, non-Exadata). But it doesn’t clearly tell you what’s included – and the names being used aren’t very revealing either.
… Continue reading...
Document Description Rolling RAC Patch Download Note:24448103.8 220.127.116.11.161018 Database Proactive Bundle Patch