I am thinking of Linus Torvalds development rule of "Do no harm, don't break
users."
My main issue with PDB, or at least the issue I think exists until I have had a
chance to work with it more, is it breaks things (scripts, workflows,
monitoring).
Perhaps there may have been a way to achieve PDB as an abstraction that looked
the same as always but was in fact single PDB. Not sure and the engineering
challenges I am sure are ginormous.
Also suspect that changes like this are initially architected more for Oracle's
financial and strategic (Oracle Cloud?) interests more so than that of the
customer base.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Tim Hall
Sent: Wednesday, April 17, 2019 12:16 PM
To: Andrew Kerber <andrew.kerber@xxxxxxxxx>
Cc: oracledbaquestions@xxxxxxxxx; ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: Re: Does anyone find PDB/CDB DBs have value?
Hi.
Check out the CONTAINERS clause. You can query across containers with that. If
you don't like that, you can use catcon.pl to perform and action in each PDB,
including queries.
Full disclosure. I'm a fan. I even like them with Lone-PDB, which is what we
use in our company. We don't have the multitenant option, so this is all we can
sensibly use. Even then there are some neat things.
We do a lot of cloning to refresh Dev/Test environments. Prior to PDBs, that
meant doing RMAN clones (typically active). They are all scripted and work, but
it's so much easier to throw in:
CREATE PLUGGABLE DATABASE devpdb FROM prodpdb@prod_link; ALTER PLUGGABLE
DATABASE devpdb OPEN;
Since the CDB is already there, with backup schedules in place and registered
with Cloud Control, there is no messing about. It cuts down on the scripting
and the post-clone cleanup.
Upgrades and patches are a little quicker if you want to just patch the PDB,
rather than the CDB and the PDB at once. You can build your new patched CDB,
then when everything is sorted and you are happy it's all good, just
upgrade/patch the PDB using the unplug/plugin method.
I've written a bunch about it all here, but I'm still learning.
https://oracle-base.com/articles/12c/multitenant-overview-container-database-cdb-12cr1#multitenant-articles
I suppose one of the big factors in my mind is, this is that way it is now. You
might not like the multitenant architecture, but Non-CDB is deprecated and will
be removed in a future release, so you might as well get used to it. We only
use non-CDB if forced to my external factors, like vendors not understanding
it. :)
Cheers
Tim...
--
//www.freelists.org/webpage/oracle-l
