When you patch, please use UPDATES – and not REVISIONS

I can just repeat what I’m saying not for almost a year: When you patch, please use UPDATES – and not REVISIONS. Updates (or Release Updates – short: RU) and Revisions (or Release Update Revisions – short: RUR) are patch bundles for the Oracle Database since Oracle 12.2.0.1. There are no PSUs (Patch Set Updates) anymore. And Revisions are not the same as PSUs. When you patch, please use UPDATES – and not REVISIONS One of the reasons why we recommend Updates, and not Revisions, simply is: Updates keep you more current whereas Revisions will let you miss a lot…

Patching to Oracle 18.2.0 in the Oracle Cloud (OCI Classic)

I was quite surprised when I spotted the Update (RU) Oracle 18.2.0 mid of April in my OCI Classic (DBCS, DBaaS) account. Of course I was thrilled immediately and started the patching to Oracle 18.2.0 in the Oracle Cloud (OCI Classic). Patching to Oracle 18.2.0 in the Oracle Cloud (OCI Classic) The April 2018 Updates (and Bundle Patches and Patch Set Updates for Oracle releases below 12.2) got released on April 17, 2018. You can read more here on how I applied all of them to my Oracle 11.2.0.4, 12.1.0.2 and 12.2.0.1 databases. But I was positively surprised when I…

Purging of PDB_PLUG_IN_VIOLATIONS in Oracle 18c

PDB_PLUG_IN_VIOLATIONS is a strange view in the Oracle database universe. It does not follow Oracle naming conventions – and it has too many underscores in its name. Furthermore I get always annoyed by the fact that it doesn’t get purged automatically. In addition it accumulates a massive number of useless information over time. But in Oracle Database 18c there’s a least some relief: A new call gets introduced which allows purging of PDB_PLUG_IN_VIOLATIONS in Oracle 18c. PDB_PLUG_IN_VIOLATIONS As others have written a lot already about PDB_PLUG_IN_VIOLATIONS I won’t repeat it but rather share the links with you: https://martincarstenbach.wordpress.com/2016/06/29/tales-from-the-field-potential-reasons-for-pdb-plug-in-violations-part-1/ https://martincarstenbach.wordpress.com/2016/07/14/tales-from-the-field-potential-reasons-for-pdb-plug-in-violations-part-2/ https://blog.dbi-services.com/12c-multitenant-internals-pdb_plug_in_violations/…

Oracle Database 18c: A new preupgrade.jar is available

In case you plan to upgrade a database to Oracle Database 18c: A new preupgrade.jar is available for download from MyOracle Support (MOS). Oracle Database 18c: A new preupgrade.jar is available Please download it – as always – from MOS Note:884522.1. The same MOS note will get you also the most recent versions of the preupgrade.jar for Oracle Database 12.2.0.1 upgrades. Of course you can download also all previous incarnations such as preupgrd.sql for 12.1.0.2 upgrades and even utlu112i.sql for 11g upgrades. What’s new in preupgrade.jar for Oracle 18c upgrades? There are a few important and good Improvements and new…

DBMS_OPTIM_BUNDLE Package in Oracle 12.2 and 18c

Yes, I did blog about the DBMS_OPTIM_BUNDLE package in earlier Oracle releases before. And I thought (and it was documented this way) that it will disappear in Oracle 12.2 and newer. But in fact you’ll find the DBMS_OPTIM_BUNDLE package in Oracle 12.2 and 18c. Most likely … This is a very interesting case and you may see also my previous blog posts: DBMS_OPTIM_BUNDLE – only available in Oracle 12.1.0.2 – or not? Fixes for Adaptive Features are included in Oracle 12.1.0.2 October 2017 BP Package Differences between Oracle 11.2.0.4 and 12.1.0.2? DBMS_OPTIM_BUNDLE Package in Oracle 12.2 and 18c First of…

Oracle Database 18c – Some important changes

I know that Oracle Database 18c is available in the Oracle Cloud and on Exadata engineered systems only right now. But actually I’ve had conversations with some customers who downloaded Oracle 18c on-prem software for Exadata and installed it on their systems. Therefore it may be useful to talk about Oracle Database 18c – Some important changes. Oracle Database 18c – Some important changes I will highlight some important changes but of course won’t cover all of them here. Installation You may recognize the first change after downloading the image: The installation and configuration of Oracle Database software is simplified…

When does patching end for Oracle Database 12.2.0.1?

This question is coming up on a regular basis for obvious reasons whenever we speak to customers about Oracle Database 12.2 and 18c: When does patching end for Oracle Database 12.2.0.1? When does patching end for Oracle Database 12.2.0.1? Actually Roy and I are explaining this topic in our The New Release and Patching Model presentation: Annual releases, such as Oracle 12.2.0.1, Oracle 18c, Oracle 19c and so on, get a minimum of 2 years patching after the succeeding release is available. This means, as soon as Oracle 18c is available, the previous release – Oracle Database 12.2.0.1 – will…

MOS Note:742060.1 got updated with Oracle 18c information

From the Support’s Hot Topics email I learned the other day that MOS Note:742060.1 (Release Schedule of Current Database Releases) got updated with Oracle 18c information on January 18, 2018. What got added to MOS Note:742060.1? A column for Oracle 18c got added to the table of releases. You will find not information about potential release availability for Oracle 18c in the various options of the Oracle Cloud, and of course for on-premises as well. Furthermore please find the updated graph as well.     The note below the graph is very important. See MOS Note:742060.1 for further details. –Mike

Cloning a PDB from Oracle 12.1 to Oracle 12.2

Is cloning a PDB from Oracle 12.1 to Oracle 12.2 possible? A colleague raised this question recently. And a customer did ask me the same question a few days before at a user group conference. There are several ways to move a PDB from Oracle 12.1. to 12.2. But the documentation does not say explicitly if you can do a cloning operation between Oracle 12.1 and 12.2. Cloning a PDB from Oracle 12.1 to Oracle 12.2 You can clone a non-CDB and make it a PDB but you need to run noncdb_to_pdb.sql afterwards. When I wrote this blog post, Oracle…