Skip to Main Content

Breadcrumb

May 4th

Question and Answer

Connor McDonald

Thanks for the question, Roberto.

Asked: September 08, 2015 - 6:07 am UTC

Last updated: October 09, 2016 - 1:23 am UTC

Version: 12c

Viewed 10K+ times! This question is

You Asked

Tom.

If we upgrade our 11g database to 12c 12.1.0.2, can we still use the non-cdb model?

With 11g going into extended support very soon we would like to upgrade to 12c however, we are not familiar with PDBs yet so we would prefer to move into 12c and run in non-cdb mode for a while until we are ready to jump into a CDB with a single PDB.

Do you see any issues with that?

Thank you very much.

and Chris said...

Going with the multitenant architecture is the recommended approach. From the docs:

The non-CDB architecture is deprecated in Oracle Database 12c, and may be desupported and unavailable in a release after Oracle Database 12c Release 2. Oracle recommends use of the CDB architecture.


https://docs.oracle.com/database/121/UPGRD/deprecated.htm#BABDBCJI

There remains some features that are either unavailable or restricted for multitenant in 12.1.0.2 however:

https://docs.oracle.com/database/121/READM/chapter12102.htm#READM120

If you use these features then it may be better to stick with the non-CDB model.

Rating

  (5 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Deprecated vs not supported

Roberto, September 08, 2015 - 3:59 pm UTC

Yes, I saw that in the documentation however I also saw the following post which talks a bit more about deprecation.

https://blogs.oracle.com/UPGRADE/entry/non_cdb_architecture_of_oracle

Any thoughts?
Thanks
Chris Saxon
September 18, 2015 - 3:39 am UTC

"Deprecation" means "at some stage in future, we *might* stop doing enhancements on this features, and at some stage after that, we *might* no longer support it".

Does it mean you should stop using it straight away ? No. But it means in terms of your future strategies, you should keep it in mind.

Hope this helps.

Deprecation

Jeff, September 08, 2015 - 4:30 pm UTC

I wouldn't worry too much about deprecation. There are features that have been deprecated for as long as I've been working with Oracle (> 20 years) that are still hanging around - CHAR datatype comes to mind.

Alexander, June 29, 2016 - 2:52 pm UTC

How would that work if they removed support for non-cdbs? So in order to use Oracle going forward, you would have to pay standard licensing fees plus the multitenancy option just to use Oracle? Maybe that's just a tactic to scare people into buying that option :P
Chris Saxon
June 30, 2016 - 1:35 am UTC

No you're reading it wrong.

A multitenancy license is only require if you intend to have *more* than 1 pluggable database within a container (so you get all the benefits that come with that, eg thin provisioning, snapshots etc etc).

A container database with a single pluggable database does *not* require any additional licensing. So it's reasonable to assume, that at some point in the future, a "non-cdb" will convert to a "single pluggable"

hope this helps.

Alexander, June 30, 2016 - 3:04 pm UTC

Ahhh yes that is very helpful thanks!
Chris Saxon
July 01, 2016 - 2:23 am UTC

Glad we could help

A reader, October 08, 2016 - 7:05 am UTC

I download oracle 12c .
and fire v$version query :-
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
but I could not download or getting Enterprise Manager for this version .
can you help me for em manager so i can use gui?

More to Explore

Multitenant

Need more information on Multitenant? Check out the Multitenant docs for the Oracle Database