I received a question whether the Non-CDB architecture still exists in Oracle Database 12.2.from 3 different colleagues in the past week:
“Does Oracle Database 12.2 still allow us to create non-CDB databases?”
And as I get this question at every customer-facing workshop these days as well before being able to talk about Single/Multitenant – I think it is important to clarify it. The statement is misleading. And I can’t blame anybody about misreading it.
Is the non-CDB architecture still available/supported in Oracle Database 12.2?
I did blog about it a while ago – but Google is not always your friend to direct you to the right answer:
whereas you will find the difference between “Deprecated” and “Desupported” described here:
Why did we announce such a statement?
You may ask yourself: why did we announce such a statement? Of course there’s a simple reason for it. If we plan to desupport anything in the future we usually release a deprecated notice upfront to allow you planning upfront. And sometimes – just remember the desupport notes about LONG and VARCHAR, or about the Rule Based Optimizer – even desupported things stay in the database and get used. Desupported features and products don’t necessarily disappear. It could happen, or may not happen.
The non-CDB (or stand-alone) architecture is still available in Oracle Database 12.2. You can install/deploy your databases exactly as you did in previous releases. Even though I would recommend you to test and experiment with the Single-/Multitenant (CDB) architecture to learn about the benefits and flexibility already today, there’s no forced push to adopt Single-/Multitenant at the moment.