July 2018 Update, Revision, BPs, PSUs – delays and other issues

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 obvious as we…

Patching my databases with the July 2018 PSU, BP and RU

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…

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…

When you patch, please use UPDATES – and not REVISIONS

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 12.2.0.1. 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…

Do you have to execute “datapatch” when you create a new database?

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 SQL changes, for instance a new…

January 2018 Database RU and RUR got released

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: Critical Patch Update – January 2018 Risk Matrix for Oracle Database Then you’ll see that there are three fixes included for vulnerabilities which may be remotely exploitable without authentication,…