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.
Starting from Apr2016 onwards the prior Database Bundle that was called “Database patch for Engineered Systems and Database In-Memory 22.214.171.124” will now be called “Proactive Bundle Patch 126.96.36.199”. 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 188.8.131.52”.
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
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.
- 184.108.40.206 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 – 220.127.116.11 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
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:
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 18.104.22.168.160719 DBPSU
- It is already removed from all the other platforms