Can you apply Bundle Patches (BP) to Standard Edition (SE2) databases?
This question got raised by Adam (thanks!) via the comments section of the blog. But a few days later I read it on the internal mailing lists as well. Adam was referring to this sentence in the BP READMEs since October 2015:
“In this document Oracle Database Home refers to Enterprise Edition.
All credits go to Ricardo Maeda as I knew that we’ll release a Bundle Patch for Oracle 220.127.116.11 sometime this week – but I couldn’t find it linked from the usual MOS notes. And please don’t ask my why that is.
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.… [Read More]
New Parameters in Oracle Database 18.104.22.168 with July 2016 PSU/BP
By following an internal discussion and checking parameter changes between Patch Set Updates (PSU) and Proactive Bundle Patches (BP) I learned that we introduced two new SPFILE parameters in Oracle Database 22.214.171.124 with the July PSU and BP. One is documented in the patch readme, the other one can be found right now only in the Oracle Database 126.96.36.199 manual:
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.… [Read More]