Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Fourth shutdown option

Re: Fourth shutdown option

From: Van Messner <vmessner_at_bestweb.net>
Date: Tue, 31 Oct 2000 23:11:11 GMT
Message-ID: <jkIL5.86$ad.10092@newshog.newsread.com>

What made me think there was a timing element is the message in OEM when you select this option.

Van

"David Fitzjarrell" <oratune_at_aol.com> wrote in message news:8tmkqp$nfv$1_at_nnrp1.deja.com...
> In article <l5qL5.10647$mC.722891_at_monger.newsread.com>,
> "Van Messner" <vmessner_at_bestweb.net> wrote:
> > Thanks,
> >
> > We'd found the reference you mentioned. There is also a very
 limited
> > set on Metalink. And OEM is how we first found out about this
 option. I'm
> > still curious as to why this shutdown transactional is never
 mentioned along
> > with shutdown normal, shutdown immediate and shutdown abort. That
 includes
> > third-party books as well as Oracle documentation. Also, I'd still
 like to
> > know specifically how we set the timing.
> >
>
> According to the documentation (reprinted below to refresh one's
> memory) there is no time limit for existing transactions to complete
> therefore there would be no provision to set timeout values for the
> shutdown:
>
>
> SHUTDOWN TRANSACTIONAL;
>
> After submitting this statement, no client can start a new transaction
> on this particular instance. If a client attempts to start a new
> transaction, they are disconnected. After all transactions have either
> committed or aborted, any client still connected to the instance is
> disconnected. At this point, the instance shuts down just as it would
> when a SHUTDOWN IMMEDIATE statement is submitted.
>
> A transactional shutdown prevents clients from losing work, and at the
> same time, does not require all users to log off.
>
>
> The SHUTDOWN TRANSACTIONAL prohibits NEW transactions against the
> instance; it DOES NOT limit the length of time existing transactions
> have to complete, hence no TIMEOUT parameter is available. Also, as
> far as I know, there are no init<SID>.ora parameters to set to
> configure transaction timeout values (although there could be
> some 'hidden' parameter, undocumented by Oracle, that does this).
>
> --
> David Fitzjarrell
> Oracle Certified DBA
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Tue Oct 31 2000 - 17:11:11 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US