Regarding #1 below (and in my experience).
While Oracle is using PDB’s by default in their cloud, I am able to create
non-PDB/traditional databases with the dbcli create-database command in our OCI
(nee Bare Metal) environment. Something like this:
dbcli create-database -n testdb -cl OLTP -s odb4 -v 12.1.0.2 -no-c -u testdb
-hm <your-strong-password-here>
The “-no-c” parameter means no container.
https://docs.cloud.oracle.com/iaas/Content/Database/References/dbacli.htm
I do not know of a way to create a non-CDB database through the cloud console.
Not that I really looked. Old fart + command line = ME.
-joe
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Neil Chandler
Sent: Wednesday, August 29, 2018 7:24 AM
To: niall.litchfield@xxxxxxxxx
Cc: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: Re: Create 12c or 18c database in traditional architecture
Personally I think multi-tenant a decent feature but it is cost prohibitive for
what you get in return.
There's not enough compelling functional reasons to migrate to the single-PDB
model... except for 2 items:
1. What are Oracle using in the Cloud? PDB's. It's only a small percentage
of the Oracle installed base at present but that will grow and become the norm.
2. What do Oracles regression tests run against? I don't know the answer to
this but I suspect that they mostly run against PDB's now. It's like the old
Block Size argument - which block size should you use (answer: 8k only - unless
you have a proven case to change size). Oracle regression tests run against 8k
and 16k block sizes. There are few (if any) regressions against 32k block sizes
in a normal regression run, although that's changing apparently.
I'd imagine its the same with PDB's (and I'm now going to try to find out,
unless someone on here knows?) If all of the regressions run against the
multi-tenant code path, you should be using the single-PDB model as it'll have
fewer bugs.
I see about a 20% adoption rate at my clients of single PDB at the moment, and
nobody rushing to embrace it except Tim 😎
Neil Chandler
Database Guy.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>> on behalf
of niall.litchfield@xxxxxxxxx<mailto:niall.litchfield@xxxxxxxxx>
<niall.litchfield@xxxxxxxxx<mailto:niall.litchfield@xxxxxxxxx>>
Sent: 29 August 2018 12:21
Cc: ORACLE-L
Subject: Re: Create 12c or 18c database in traditional architecture
Hi Yong
We've gone with the traditional architecture so far, the primary reason for
this is that administration scripts and utilities that use ORACLE_SID and/or
TWO_TASK will all require rewriting to ensure they continue to work. Frankly,
we have an incomplete handle on all the available scripts on our several
hundred Oracle servers and almost no view of the ad-hoc etc scripts that
development teams may have placed on our DB servers. Certifying and
communicating the change is also a not insignificant effort for a pretty small
Engineering team. That said our aim is definitely to migrate to the PDB
architecture the 12.2 "family" of releases timescale. We absolutely do not want
to be in a position where we *have* to move faster than we actually can!
Similarly, we've not looked yet at FlexASM but we will do in a potential
feature release.
I don't see single PDB being buggier than the traditional release (I can see
that there will be bugs around the new features of multi-tenant) and its not
true that there's no MGMTDB in a traditional architecture (and from 12.1.0.2 it
will be a single instance pdb ! ).
On Tue, Aug 28, 2018 at 5:02 PM Yong Huang
<dmarc-noreply@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>> 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
--
Niall Litchfield
Oracle DBA
http://www.orawin.info<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.orawin.info&data=02%7C01%7CJSweetser%40icat.com%7Cf2dc82017fee440f33a508d60db2dd85%7C5d3bf30e9adb4c17b2425c17523e6e5e%7C0%7C0%7C636711459218721533&sdata=vBRE9LUQU82wYvfuZjgCM3l%2Bhwb3vb7mYlNso4ii664%3D&reserved=0>
This e-mail transmission and any attachments that accompany it may contain
information that is privileged, confidential or otherwise exempt from
disclosure under applicable law and is intended solely for the use of the
individual's to whom it was intended to be addressed. If you have received this
e-mail by mistake, or you are not the intended recipient, any disclosure,
dissemination, distribution, copying or other use or retention of this
communication or its substance is prohibited. If you have received this
communication in error, please immediately reply to the author via e-mail that
you received this message by mistake and also permanently delete the original
and all copies of this e-mail and any attachments from your computer. Please
note that coverage cannot be bound or altered by sending an email. You must
receive written confirmation from a representative of our firm to put coverage
in force or make changes to an existing policy.
