RE: Re: Does anyone find PDB/CDB DBs have value?

From: Testa, Joseph S <TESTAJ3_at_nationwide.com>
Date: Wed, 17 Apr 2019 17:23:06 +0000
Message-ID: <BL0PR07MB39545D9E563ED9B4C7248F4C97250_at_BL0PR07MB3954.namprd07.prod.outlook.com>


This statement is your friend to "peek" inside PDBs from the container with a common user:

ALTER USER C##COMMON_USER SET CONTAINER_DATA=ALL CONTAINER=CURRENT; <-- in the CDB and replace C##COMMON_USER with your common userid of choice.

Joe



Quit doing what is easy and do what is right.

Joseph Testa
Database Services Security

-----Original Message-----
From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of Tim Hall Sent: Wednesday, April 17, 2019 1:16 PM To: Andrew Kerber <andrew.kerber_at_gmail.com> Cc: oracledbaquestions_at_gmail.com; ORACLE-L <oracle-l_at_freelists.org> Subject: [EXTERNAL] Re: Does anyone find PDB/CDB DBs have value?

Nationwide Information Security Warning: This is an external email. Do not click on links or open attachments unless you trust the sender.


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_at_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...

On Wed, Apr 17, 2019 at 5:51 PM Andrew Kerber <andrew.kerber_at_gmail.com> wrote:
>
> To me the appear to be a solution in search of a problem.
>
> On Wed, Apr 17, 2019 at 8:43 AM Dba DBA <oracledbaquestions_at_gmail.com> wrote:
>>
>> So far I have to treat it basically like separate DBs. I log into the root DB, but to look at v$ views or do maintenance I have to open each individual DB. If oracle figures out a way to run reports against the data dictionary for all DBs I think it will be more useful. I have not really looked at version 18 yet so not sure if they added much for PDB/CDBs.
>>
>> What do others think?
>
>
>
> --
> Andrew W. Kerber
>
> 'If at first you dont succeed, dont take up skydiving.'
--
http://www.freelists.org/webpage/oracle-l

†Ûiÿü0ÁúÞzX¬¶Ê+ƒün– {ú+iÉ^ Received on Wed Apr 17 2019 - 19:23:06 CEST

Original text of this message