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

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 11.2.0.4, Oracle 12.1.0.2 and Oracle 12.2.0.1 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 – and…

The first RU for Oracle Database 12.2.0.1 is available

The first RU (Release Update) for Oracle 12.2.0.1 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: http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html Find the Risk Matrix for the July 2017 Critical Patch Advisory here: http://www.oracle.com/technetwork/security-advisory/cpujul2017verbose-3236625.html#DB 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…

PSU or BP? Patch Set Update or Bundle Patch? RUR or RU?

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 12.2.0.1.Changes are marked in orange. See. https://mikedietrichde.com/2017/07/19/first-ru-oracle-12-2-0-1-available/ 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 the BPs in Oracle…

DBA_REGISTRY_HISTORY vs DBA_REGISTRY_SQLPATCH

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 internally to get a…

July 2016 – Proactive BPs and PSUs are available

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. See the Oracle Critical Patch Update Advisory July 2016 for further details, and especially the Database announcement on MOS. 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. 2.1 Database patch for Engineered Systems and Database In-Memory 12.1.0.2 renamed to “Proactive Bundle Patch 12.1.0.2” Starting from Apr2016 onwards the prior Database…

Oracle April 2016 PSU and Proactive BPs are there

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: Critical Patch Update – April 2016 Patch Availablity – Oracle Database – April 2016 The important change in the April PSU/BP release: The database patch for “Engineered Systems and Database In-Memory 12.1.0.2” luckily got renamed into “Proactive Bundle Patch 12.1.0.2”. That is not only a rebranding but it should express that we would like to encourage you to apply the Bundle Patches instead…

PSU October 2014

October 14, 2014 Oracle released a new Patch Set Update. And as usual we strongly recommend that you’ll apply it as soon as possible to your databases. PSU October 2014 – General Information: http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html  There’s one fix for JAVA in it which requires to either take the database down or do some other actions. Please find a detailed description here: Eric Maurice’s security blog: https://blogs.oracle.com/security/entry/october_2014_critical_patch_update “Due to the nature of the fixes required, Oracle development was not able to produce a normal RAC-rolling fix for these issues. To help protect customers until they can apply the Oracle JavaVM component Database PSU,…