What a wonderful question: “We are on Oracle 126.96.36.199 right now. Should we wait for Oracle 19 because of the proposed long term support for this release?”
I have gotten this question roughly 15 times in the past week, raised either by colleagues, customers or partners via email, twitter, in web conferences or (old fashioned way) on the phone.… [Read More]
Well … another post about RU and RUR patches. But after having multiple discussions personally, via web conferences, in conference calls and of course on Twitter I think some clarifications may be helpful. Below you’ll find Oracle Database RU and RUR recommendations and facts. At least some of them …
Oracle Database RU and RUR Recommendations and Facts
First of all, you will find more information in several blog posts about RU (Release Update) and RUR (Release Update Revision) patches:
The DBMS_OPTIM_BUNDLE package got introduced with the April 2014 Exadata 188.8.131.52 Bundle Patch. And it got introduced for all Oracle 184.108.40.206 databases with the April 2017 Bundle Patch (BP). DBMS_OPTIM_BUNDLE is only available in Oracle 220.127.116.11.
For more information on this package on Exadata in Oracle 18.104.22.168 you may look at:
I have received several questions from customers in the past weeks using Oracle Multitenant about the parameter exclude_seed_cdb_view.It magically disappeared and morphed into _exclude_seed_cdb_view since Oracle Database 22.214.171.124. To be fair, the exclude_seed_cdb_viewis listed in the list of obsolete parameters in Oracle Database 126.96.36.199.
What is EXCLUDE_SEED_CDB_VIEW?
This parameter hides everything belonging to the PDB$SEED from the usual queries.… [Read More]