Re: Automatic startup of pluggable databases - why not the default?

From: Jared Still <jkstill_at_gmail.com>
Date: Fri, 24 Jul 2015 09:23:35 -0700
Message-ID: <CAORjz=OphVGz=Jn2WfMU-cALwexKEfXC71_yCz6hGt487rcTVg_at_mail.gmail.com>

On Fri, Jul 24, 2015 at 7:17 AM, John Hallas <John.Hallas_at_morrisonsplc.co.uk
> wrote:

> Yes I agree Brent that is the workaround that the changes in 12.1.0.2
> were meant to address. I am interested in understanding why it was not seen
> as reasonable to start the pdb databases up after a container restart

I can see why it would not be reasonable to start all PDB's at startup.

• there may be hundreds of them; you don't want to start these all at once.
• of those hundreds, possibly a fraction of them are used regularly and should be started.

What I don't understand is the lack of a proper method for dealing this this.

Neither the trigger nor the save state seem good options to me.

Why not a pdb control table with a START_MODE column?

Possible values

- NEVER:  Never open the pdb at startup
- ALWAYS: Always start this pdb.
- ON_DEMAND:  Start this pdb when someone tries to connect to it.

And then some mechanism to override this.

'startup open cdb nomount nopdb' for instance.

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist Principal Consultant at Pythian
Pythian Blog http://www.pythian.com/blog/author/still/ Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Jul 24 2015 - 18:23:35 CEST