Oracle 12.2.0.1 Bundle Patch 12.2.0.1.170516 DBBP on Linux x86-64 is available

All credits go to Ricardo Maeda as I knew that we’ll release a Bundle Patch for Oracle 12.2.0.1 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 12.2.0.1. There will be a first bigger Proactive Bundle Patch in July at the usual schedule – but this one is at least a start.

12.2.0.1.170516BP

Patch 2579308 – Oracle 12.2.0.1.170516BP

Plus in addition get the OPatch version 12.2.0.1.7 via patch 6880880.

The BP contains:

12.2.0.1.170516BP

First 12.2.0.1 Bundle Patch – Contents: Database BP and GI PSU

Obrigado, Ricardo!

–Mike

PSU or BP? Patch Set Update or Bundle Patch?

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?

Should we take the PSUs or the BPs ?

PSUs are Patch Set Updates, BPs are (sometimes called: Proactive) Bundle Patches.

And the answer is very simple:

  • If you have an Oracle Engineered System: Take the Bundle Patches for Engineered Systems
  • In all other cases:
    • If you are on Oracle Database 12.1.0.x or newer: Take the Bundle Patches
    • If you are on Oracle Database 11.2.0.4: Take the Patch Set Updates
    • If you are on a release below Oracle Database 11.2.0.4: Upgrade!

Is there an official recommendation or guideline?

Yes, of course, there’s one. Very well explained in MOS Note: 1962125.1 – Overview of Database Patch Delivery Methods:

Bundle Patch Recommendation

Recommendation for Oracle 12c: Bundle Patches

What else do you need to know?

  1. Q: Is there a difference between “Bundle Patch” and “Proactive Bundle Patch“.
    A: It’s the same thing.
  2. Q: Can I apply Exadata Bundle Patches on non-Exadata Systems in Oracle 11g?
    A: Even though this is technically possible for Linux, there are certain restrictions. This is only supported in a standby configuration where one part is operated on an Exadata. See the FAQ at the end of MOS Note: 1962125.1 – Overview of Database Patch Delivery Methods
  3. Q: Can I flip from PSUs to BPs?
    A: When you approach a release or patch set upgrade (i.e. Oracle Database 11.2.0.3 to Oracle Database 12.1.0.2, or Oracle Database 12.1.0.1 to Oracle Database 12.1.0.2) you will start from scratch and have the full choice. But in-between a release you’ll have to deinstall at least the sql changes and roll in the new sql changes when you change between PSUs and BPs or vice versa. See my previous blog posts about switching from PSUs to BPs: https://mikedietrichde.com/2016/05/03/can-i-apply-a-bp-on-top-of-a-psu-or-vice-versa/
  4. Q: Why does Oracle still deliver PSUs in Oracle 12c even though it recommends to use the BPs?
    A: I don’t know. I can just assume that some customers insist to get the PSUs having a smaller number of fixes meaning potentially lower effect on their systems. But personally I totally disagree. When you look up the current issues list for Oracle 12.1.0.2 you will find out that many of the fixes are included in the BPs but not in the PSUs. If it would be my choice, I can perfectly (and better) live without PSUs but only getting BPs instead.
  5. Q: I have issues with the patches’ readme – can you explain it to me?
    A: No. Please log an SR. I get the “readme complaint” from almost every customer I see. And I see all the points and agree in most of them. Still, I’m not the owner of patching nor the owner of the readme’s. Telling it me is good – but telling it Oracle Support via an SR, and force a bug to be logged is the much better solution. Please please please, do log SRs when you are not happy with the patches’ readme, when things are unclear or wrongly carried over or whatever. The readmes get written by humans and they will need your feedback to improve the readmes.

–Mike

October 2016 PSU and BP – Database Patching?

What will you get when you download the most recent Oracle Database PSU or BP from October 2016?

MOS Note: 1683799.1 – 12.1.0.2 Patch Set – Availability and Known Issues is not entirely clear. Therefore lets shed some light …

The Matrix

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.

Non Exadata Non RAC

Document Description Rolling RAC Patch Download
Note:24448103.8 12.1.0.2.161018 Database Proactive Bundle Patch (Oct 2016) Yes Patch:24448103
Note:24436306.8 Combo of 12.1.0.2.161018 OJVM PSU and 12.1.0.2.161018 DBBP (Oct 2016) Part Patch:24436306
Note:24433133.8 Combo of 12.1.0.2.161018 OJVM PSU and 12.1.0.2.161018 DB PSU (Oct 2016) Part Patch:24433133
Note:24315824.8 Oracle JavaVM Component 12.1.0.2.161018 Database PSU (Oct 2016) (OJVM PSU) No Patch:24315824
Note:24006101.8 12.1.0.2.161018 (Oct 2016) Database Patch Set Update (DB PSU) Yes Patch:24006101

My Matrix

I translate this into:

Non Exadata Non RAC

Document Description Rolling RAC Patch Download DB PSU DB BP GI PSU OJVM
Note:24448103.8 12.1.0.2.161018 Database Proactive Bundle Patch (Oct 2016) Yes Patch:24448103 X X
Note:24436306.8 Combo of 12.1.0.2.161018 OJVM PSU and 12.1.0.2.161018 DBBP (Oct 2016) Part Patch:24436306 X X X
Note:24433133.8 Combo of 12.1.0.2.161018 OJVM PSU and 12.1.0.2.161018 DB PSU (Oct 2016) Part Patch:24433133 X X
Note:24315824.8 Oracle JavaVM Component 12.1.0.2.161018 Database PSU (Oct 2016) (OJVM PSU) No Patch:24315824 X
Note:24006101.8 12.1.0.2.161018 (Oct 2016) Database Patch Set Update (DB PSU) Yes Patch:24006101 X

How to apply a Proactive Bundle Patch?

If you’ve never done it before, applying a Proactive Bundle Patch to a database-only installation is not very complicated. Please see my own step-by-step instructions here (but don’t forget to check the current readme as well please!).

More Information:

–Mike

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 Bundle that was called “Database patch for Engineered Systems and Database In-Memory 12.1.0.2” will now be called “Proactive Bundle Patch 12.1.0.2”. This patch will continue be a cummulative patch and will include all prior fixes. The Apr2016 Proactive BP can also be applied on top the Jan2016 “Database patch for Engineered Systems and Database In-Memory 12.1.0.2”.

Does Oracle really recommend the Proactive Bundle Patches?

Well, I blogged about it almost 3 months ago and received several emails and comments from customer and colleagues sending me either complaints or SRs where somebody in Oracle Support gave them a hard time as one has applied a Proactive Bundle patch on a non-Exadata system. Hm … the fact the Proactive BPs were available in Solaris, AIX and HP-UX as well got simply ignored. Sorry for the inconvenience – but Oracle is a big ship and sometimes it takes a while until the message reaches really everybody.

Anyhow, in case you get into discussion with Oracle Support people in an SR please direct them to MOS Note: 1962125.1 – Oracle Database – Overview of Database Patch
Delivery Methods
:

Oracle makes the following recommendation for which patch method to use for Database related installations:

  • Every customer should at least install PSUs. Minimal testing required.
  • 12.1.0.2 Customers wanting a more comprehensive set of fixes should install the Database Proactive Bundle patch. This requires a bit more testing than a Patch Set Update (PSU), but delivers a larger set of fixes

1 The “Database Proactive Bundle Patch” requires a bit more testing than a Patch Set Update (PSU) as it delivers a larger set of fixes. 

[above table and text is taken from MOS Note:1962125.1 as of July 20, 2016]

Other changes you should be aware of?

And you’ll find also significant changes in the naming in MOS Note:1683799.1 – 12.1.0.2 Patch Set – Availability and Known Issues. The Recommended Patches section differentiates now between Exadata, RAC and non-RAC systems making your choice much easier, and removes the misleading naming for DBIM:

Non Exadata Non RAC

Document Description Rolling RAC Patch Download
Note:23615334.8 Combo of 12.1.0.2.160719 OJVM PSU and 12.1.0.2.160719 DBBP (Jul 2016) Part Patch:23615334
Note:23615289.8 Combo of 12.1.0.2.160719 OJVM PSU and 12.1.0.2.160719 DB PSU (Jul 2016) Part Patch:23615289
Note:23273686.8 12.1.0.2.160719 Database Proactive Bundle Patch (Jul 2016) Yes Patch:23273686
Note:23177536.8 Oracle JavaVM Component 12.1.0.2.160719 Database PSU (Apr 2016) (OJVM PSU) No Patch:23177536
Note:23054246.8 12.1.0.2.160719 (Jul 2016) Database Patch Set Update (DB PSU) Yes Patch:23054246

I’d recommend you the one in BOLD letters unless you use OJVM and require the OJVM patch in addition.

And finally … the summary!

For those who have no time to read such a lengthy blog post here’s the important facts:

–Mike

[Addition/Update] 

Please be aware of:

  • BUG 24332805 – OUI-67124:RE-LINK FAILS ON TARGET “ISQORA” DURING JUL 2016 PSU APPLY”
  • Two workarounds:
    • Addition of UnixODBC package to server
      • Install the “unixODBC” packages:
        yum install unixODBC
      • Re-run the ins_odbc.mk
        • cd $ORACLE_HOME/odbc/lib/
        • make -f ins_odbc.mk isqora
    • Removing the sqora relinking from ‘actions.xml’ file of Linux x86-64 12.1.0.2.160719 DBPSU
      • It is already removed from all the other platforms