Re: Automatic startup of pluggable databases - why not the default?
From: Brent Day <coloradodba_at_gmail.com>
Date: Fri, 24 Jul 2015 08:14:37 -0600
Message-ID: <CAEz8shw=W60WEEYAAC=qzhB0aU3BiPQan+j9LmC+2L68gus6LQ_at_mail.gmail.com>
You could create a database trigger after startup that has the following
Date: Fri, 24 Jul 2015 08:14:37 -0600
Message-ID: <CAEz8shw=W60WEEYAAC=qzhB0aU3BiPQan+j9LmC+2L68gus6LQ_at_mail.gmail.com>
You could create a database trigger after startup that has the following
execute immediate 'alter pluggable database all open';
Brent
On Fri, Jul 24, 2015 at 6:18 AM, John Hallas <John.Hallas_at_morrisonsplc.co.uk
> wrote:
> Now 12.1.0.2 allows you to save a state in advance using ‘alter pluggable
> database xxx save state’ which does seem a step forward
>
>
>
> However why would the default not be to start all the pluggable databases
> (or services as they are seen) not leave them in a mounted state. Obviously
> Oracle have thought about this and changed the trigger method, maybe due to
> customer feedback but I wonder why they have not gone the whole hog and
> started the services automatically.
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Jul 24 2015 - 16:14:37 CEST