Do you remember? At OOW 2019 in San Francisco, we announced that Oracle Database 20c will be the first CDB-only database release. But at this time we didn’t present this in written form. We told you, once the Oracle Database 20c documentation is available, you will see it. Oracle Database 20c – The first CDB-only release.
Photo by Belinda Fewings on Unsplash
Oracle 20c is the first CDB-only release
Typically you will find deprecation and desupport notes in the Database Upgrade Guide. And there you will see also this note:
Desupport of Non-CDB Oracle Databases
Starting with Oracle Database 20c, installation of non-CDB Oracle Database architecture is no longer supported.
The non-CDB architecture was deprecated in Oracle Database 12c. It is desupported in Oracle Database 20c. Oracle Universal Installer can no longer be used to create non-CDB Oracle Database instances.
What does this mean for you?
At first, most of you will move to Oracle Database 19c right now. So you may not care about Oracle Database 20c yet. In Oracle Database 19c, the non-CDB and the CDB architecture stand side-by-side, you can choose either one. And since Oracle Database 19c, 3 PDBs are included. Just make sure you use max_pdbs=3 in your SPFILE.
Hence, nothing changes right now.
As of now, MOS Note:742060.1 – Release Schedule of Current Database Releases hasn’t been updated yet. But it is expected that Oracle 20c will get only a shorter support time frame as the terminal release of the release family. I assume that you will consider 20c only to test out certain development features but you will target the next terminal release of the 20c family as the one you will upgrade to.
But when you attempt this move, this means you will migrate your database unless it isn’t a CDB/PDB already. And when you plan this, please browse through the blog posts I wrote a few months ago. Some things may need extra consideration. And I may extend the list of things to know over time.
I just would like to quote Tim Hall here:
Further Information and Links
- Oracle Database 20c – Documentation and Cloud availability
- 3 PDBs included – and non-CDB architecture desupported
- Database Migration from non-CDB to PDB – An Overview
- Upgrade, plug in, convert (noncdb_to_pdb.sql) – 11.2.0.4 and higher
- Plugin, upgrade, convert (noncdb_to_pdb.sql) – 12.2.0.1 and higher
- Clone via NON$CDB, upgrade, convert – 12.1.0.2 and higher
- Typical Plugin Issues and Workarounds
- The Compatible Pitfall
- The Time Zone Pitfall
- The Component Pitfall
- The Patch Level Pitfall
- Various Pitfalls
- The Fallback Challenge
- The Minimal Downtime Challenge
–Mike
Just one question: we have to create put our data in PDB’s. But can we create as many cdb’s as we want, each with 3 pdb’s?
We have oracle SE 12.2 with 5 databases.
We have oracle EE 12.2 rac with 6 databases. Buying Container edition is a big cost just to do what we could do. I can telkl the same about RAC removed from Oracle SE. Thanks.
Alain,
CDBs are treated as regular non-CDB databases were. Hence, no change. If you have 6 non-CDB databases right now, you can have 6 CDBs afterwards as far as I’m aware. There shouldn’t be a change. Well, and regarding the RAC removal with SE in 19c, I know exactly what you mean 🙁
Thanks,
Mike
nice article
Thanks!
Currently AWR Warehouse repository database doesn’t support PDB. You have to create non-CDB database. Will this change with 20c?
I’D guess so – in 20c, there are non-CDBs anymore.
Cheers,
Mike
Mike,
Currently, I can upgrade 11g to 19c non-CDB and then unplug this non-CDB and plug as a PDB into an existing 19c CDB. Would this approach work in 20c?
Thanks,
Arun
Hi Arun,
autoupgrade will choose a different approach – and the standard upgrade will require the same:
1. Plugin
2. Upgrade
Otherwise you’d have a 20c non-CDB which is not possible.
11g databases can’t be upgraded directly to 20c and further – it has to be 12.2.0.1 at least.
Cheers,
Mike