Re: Create 12c or 18c database in traditional architecture
Date: Wed, 29 Aug 2018 11:41:50 +0800
Message-ID: <CAMNBsZuTXPVt1-4DesvtYDdfh6mHA5x5k_C__BxcvWdNO-a-+w_at_mail.gmail.com>
If you creating a *new* database for a new application you should prefer Single Tenant PDB.
However, if you are going to use existing administration code, backup scripts, monitoring scripts etc that run on the database server and use ORACLE_SID instead of TWO_TASK / TNS, you'd have to modify them -- and that means they will diverge from the "standard" scripts being used in other environments.
Similarly, if you have an application that runs on the same server and uses ORACLE_HOME and ORACLE_SID instead of TWO_TASK / TNS, it would need to change.
The question would be if you (i.e. the DBA team) are willing to make those changes to the admin/backup/monitoring scripts and application configuration and maintain those changes going forward ?
Hemant K Chitale
On Wed, Aug 29, 2018 at 12:02 AM Yong Huang <dmarc-noreply_at_freelists.org> wrote:
> When creating a 12c or 18c database without the multitenancy license, I
> can (1) create the database with one CDB and only one PDB, or (2) create
> the database in the traditional or non-CDB architecture. The advantage of
> (2) is possibly less buggy, less overhead (no mgmtdb on RAC for instance),
> and slightly easier management. But the disadvantage is that Oracle does
> not recommend it and that "(t)he non-CDB architecture was deprecated in
> Oracle Database 12c. It can be desupported and unavailable in a release
> after Oracle Database 19c."
>
> Short of a formal survey, I'd like to know which option you all have
> chosen. Thank you!
>
> Yong Huang
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 29 2018 - 05:41:50 CEST