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...
Well, there is no Product Manager for patching. And I’m glad that I’m not in this position. But thanks to all of you, internally and externally, who share your findings with me. In this blog post I’d like to inform you about the newest patching surprises – and how to fix some of them.
Patch apply without confirmation?
Peter Lehmann informed me about this a few weeks ago. Peter told me that he patched systems with the July 2019 RU for Oracle 22.214.171.124 and recognized that the patch installed with opatch without waiting for confirmation. It looked as somebody has …Continue reading...
It’s patching day. And I’m already downloading the patch bundles for all my installations (126.96.36.199, 188.8.131.52, 184.108.40.206, 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
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...
Yesterday I wrote about how to adjust the time zone setting in the
PDB$SEED as by default the time zone scripts won’t touch the
PDB$SEED when you execute them. And in addition, MOS Note:1509653.1 tells you, that the
PDB$SEED can’t be adjusted. But this leads to a weird mix of time zone settings across a Multitenant deployment. Which I’d guess is not desired. Following a tweet reply by Marco Mischke I realized: I explained how to patch the PDB$SEED – but I didn’t explain how to patch all PDBs with the a new time zone file?
Well, it is Friday night – and I’d rather should sleep or do something cool people tend to do on Friday night’s. But I try to verify a strange issue with DBMS_OPTIM_BUNDLE and the October 2018 Update for Oracle 220.127.116.11. I’m patching. Can you think of anything better on a Friday night than patching?
Of course I know that I’m not alone. I know at least two customers I work with right now who do some maintenance jobs tonight as well. And I’m struggling with OPatch … oh OPatch … why is datapatch so stubborn?
My test setup
I have …Continue reading...
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...
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
Again I’ll have to thank my colleague Roland Gräff from the German ACS Support team in Stuttgart for bringing this into our radar. Roland alerted me a week ago about an issue with exports in Oracle 18.104.22.168 only when you are on a certain patch level. I summarize the issue here under Data Pump 22.214.171.124 – Wrong Dump File Version – ORA-39142.
In the below blog post you will learn about the actual issue, where it happens and when, and of course how to workaround it.
When does it happen?
The issue I will describe below happens only with …Continue reading...
Thanks to my support colleague Roland Graeff who told me about this issue at a customer today. And I consider this a pretty serious issue. It can happen that Special characters show junk in CLOB columns after upgrade to Oracle 126.96.36.199. with JDBC.
This is as bad as it sounds. Roland told me about a case where the application showed weird characters instead of German umlauts (ä, ö, ü, Ä, Ö, Ü) after an upgrade from Oracle Database 188.8.131.52 to 184.108.40.206.
Special characters show junk in CLOB columns after upgrade to Oracle 220.127.116.11 with JDBC
Roland explained to me that …Continue reading...
In this part of my blog post series about upgrading from Oracle 18.104.22.168 to Oracle 18c I’d like to demonstrate patching Oracle Database 18.1.0 to 18.2.0 on premises.
A while ago I showed also how to patch from Oracle 18.1.0 to 18.2.0 in the Oracle Cloud.
Find the related blog posts here:
- Deinstalling Oracle Database 22.214.171.124
- Installing Oracle Database 18.1.0
- Patching Oracle 18.1.0 to 18.2.0
- Upgrade Oracle 126.96.36.199 to Oracle Database 18c on-premises
Patching Oracle Database 18.1.0 to 18.2.0 on premises
Before I can start patching to the Release Update Oracle 18.2.0 I need to download the patch …Continue reading...
Thanks to DOAG and the ORAWORLD Magazine, my article is released in the current September 2018 ORAWORLD Mag: Oracle Database Patching – Tips & Tricks
ORAWORLD Mag: Oracle Database Patching – Tips & Tricks
You’ll find my article about Database Patching – Tips & Tricks on page 28ff in the September 2018 issue if the ORAWORLD magazine. Please download it from here.
And of course, you will find other issues on the website of the ORAWORLD Magazine:
Further InformationContinue reading...
Opatch. A tool nobody really loves but everybody has to use (at least those of you who patch or aren’t in our cloud deployment). Opatch gets distributed via MOS. And you often can apply patches with an older version of OPatch. So why should you use the most recent version of OPatch?
Why should you use the most recent version of OPatch?
First of all, you have a base installation of Opatch in your
[CDB2] oracle@localhost:/u01/app/oracle/product/188.8.131.52 $ ls OPatch auto jlib opatchauto.cmd operr.bat scripts config jre opatch.bat operr_readme.txt version.txt datapatch modules opatch_env.sh oplan datapatch.bat ocm opatch.pl oracle_common docs… Continue reading...
I can just repeat what I’m saying not for almost a year: When you patch, please use UPDATES – and not REVISIONS. Updates (or Release Updates – short: RU) and Revisions (or Release Update Revisions – short: RUR) are patch bundles for the Oracle Database since Oracle 184.108.40.206. There are no PSUs (Patch Set Updates) anymore. And Revisions are not the same as PSUs.
When you patch, please use UPDATES – and not REVISIONS
One of the reasons why we recommend Updates, and not Revisions, simply is: Updates keep you more current whereas Revisions will let you miss a lot …Continue reading...
I was quite surprised when I spotted the Update (RU) Oracle 18.2.0 mid of April in my OCI Classic (DBCS, DBaaS) account. Of course I was thrilled immediately and started the patching to Oracle 18.2.0 in the Oracle Cloud (OCI Classic).
Patching to Oracle 18.2.0 in the Oracle Cloud (OCI Classic)
The April 2018 Updates (and Bundle Patches and Patch Set Updates for Oracle releases below 12.2) got released on April 17, 2018. You can read more here on how I applied all of them to my Oracle 220.127.116.11, 18.104.22.168 and 22.214.171.124 databases. But I was positively surprised when …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 126.96.36.199, Oracle 188.8.131.52 and Oracle 184.108.40.206 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 …
CORRECTION: After I published this blog post saying “April 2019” my fellow support colleagues changed the alert to “June 2019”. Just saying … the topic itself is still the same.
Simon Pane from Pythian talked to me at OUGN (Oracle User Group Norway) Conference about a recently released alert in MyOracle Support saying “Databases need to be patched to a minimum before June 2019“. He was curious if I know more details. I did some investigation but shortly afterward the MOS Note got updated as well. So here’s a quick summary of things you should be aware of …Continue reading...
I blogged about the Adaptive Features fixes in the past several times. But following some of the comments readers had I believe there’s some additional info for Adaptive Feature Fixes in Oracle 220.127.116.11 necessary.
What happened so far?
We delivered the most important fixes not only for adaptive features but only for dynamic sampling and some other things with the Database Bundle Patch in October 2017 for Oracle Database 18.104.22.168. The fixes got delivered on MS Windows a bit earlier.
- Enabling Oracle 12.2 ADAPTIVE Features in Oracle 22.214.171.124 – BEFORE the patches got included in BPs
- Oracle 12.2 Adaptive Features
It’s patching time again. The January 2018 Database RU and RUR got released. And of course other patch bundles as well. And of course not only for the database but for many other products as well. I try to summarize below the most important information and links.
January 2018 Database RU and RUR got released
First of all always have a look at the Critical Patch Alert and the Risk Matrix:
Then you’ll see that there are three fixes included for vulnerabilities which may be remotely exploitable without authentication, …Continue reading...
Well … another post about RU and RUR patches. But after having multiple discussions personally, via web conferences, in conference calls and of course on Twitter I think some clarifications may be helpful. Below you’ll find Oracle Database RU and RUR recommendations and facts. At least some of them …
Oracle Database RU and RUR Recommendations and Facts
First of all, you will find more information in several blog posts about RU (Release Update) and RUR (Release Update Revision) patches:Continue reading...
Since Oracle Database 126.96.36.199 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...