What will you get when you download the most recent Oracle Database PSU or BP from October 2016?
MOS Note: 1683799.1 – 220.127.116.11 Patch Set – Availability and Known Issues is not entirely clear. Therefore lets shed some light …
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.
Document Description Rolling RAC Patch Download Note:24448103.8 18.104.22.168.161018 Database Proactive Bundle Patch (Oct 2016) Yes Patch:24448103 Note:24436306.8 Combo of 22.214.171.124.161018 OJVM PSU and 126.96.36.199.161018 DBBP (Oct 2016) Part Patch:24436306 Note:24433133.8 Combo of 188.8.131.52.161018 OJVM PSU and 184.108.40.206.161018 DB PSU (Oct 2016) Part Patch:24433133 Note:24315824.8 Oracle JavaVM Component 220.127.116.11.161018 Database PSU (Oct 2016) (OJVM PSU) No Patch:24315824 Note:24006101.8 18.104.22.168.161018 (Oct 2016) Database Patch Set Update (DB PSU) Yes Patch:24006101
I translate this into:
Non Exadata Non RAC
|Document||Description||Rolling RAC||Patch Download||DB PSU||DB BP||GI PSU||OJVM|
|Note:24448103.8||22.214.171.124.161018 Database Proactive Bundle Patch (Oct 2016)||Yes||Patch:24448103||X||X|
|Note:24436306.8||Combo of 126.96.36.199.161018 OJVM PSU and 188.8.131.52.161018 DBBP (Oct 2016)||Part||Patch:24436306||X||X||X|
|Note:24433133.8||Combo of 184.108.40.206.161018 OJVM PSU and 220.127.116.11.161018 DB PSU (Oct 2016)||Part||Patch:24433133||X||X|
|Note:24315824.8||Oracle JavaVM Component 18.104.22.168.161018 Database PSU (Oct 2016) (OJVM PSU)||No||Patch:24315824||X|
|Note:24006101.8||22.214.171.124.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!).
- General information: Critical Patch Update – October 2016
- Risk Matrix for: Oracle Database Server, version(s) 126.96.36.199, 188.8.131.52
- Patch Availability: MOS Note: 2171485.1
- Download the Database PSU or BP:
MOS Note: 1683799.1 – 184.108.40.206 Patch Set – Availability and Known Issues
- Example on how to apply the April 16 Proactive Bundle Patch:
I attended your 12.2 Upgrade Workshop in Calgary and it’s very informative and helpful. For the question I asked about "How to remove all Windows DB Bundle Patches and back to the pure original state", can you please provide the URL links or MOC# for the steps or scripts?
To refresh background info of my question, we are on 12c (220.127.116.11) on Windows now. We encounter some weird issues while installing Jan & Apr 2016 DB & JVM BPs: passed on opatch part but getting "Nothing to apply" during post-installation step (datapatch). We have tried de-installation but seems not cleanly according to DBA_REGISTRY_SQLPATCH. There are no clear info in logs or Oracle Support thus we are looking for a clean procedure to remove any applied or "half" applied related patches from our 12c databases and bring them back to the ground zero i.e. original version 18.104.22.168.0.
Thank you in advance and hope that you could spare more time for your next trip to Calgary.
this was the blog post I mentioned:
Afterwards you’ll have to start a "datapatch -verbose" in order to clean out the SQL changes as well.
Are PSU patches truly backward compatible, if I apply Oct 2016 rdbms PSU I get all the critical, high, low fixes that were released in July 2016 PSU ?
yes, SPUs, PSUs and BPs are cummulative – if you take the Jan 17 one you’ll have all the previous fixes from either the SPUs, the PSUs or the BPs included.
I would like to know if on a fresh 22.214.171.124 GI Clusterware and RAC RDBMS is sufficient with apply GI PSU only using #opatch auto.
may I ask you to please open an SR as I’m not the master of patching?
The PSU only is correct and fine. And you should please refer to the readme – and if this is incorrect or unclear log an SR. I say this NOT to give you a bad impression but I logged 21 bugs against a single patch readme a while back – and I’d blindly say that half of them are not fixed and carried forward and forward. I get complaints about those readmes at every customer I visit when we discuss patching. And if you don’t open SRs against the readmes the responsible people will never improve the quality of those reeadmes.
I believe yes, you can use opatch auto – but again, I’m not the master of patching 😉