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: Monitor Shutdown immediate that required massive rollback

Re: Monitor Shutdown immediate that required massive rollback

From: sybrandb <sybrandb_at_gmail.com>
Date: Wed, 27 Jun 2007 01:15:18 -0700
Message-ID: <1182932118.061059.17170@k29g2000hsd.googlegroups.com>


On Jun 27, 7:56 am, Sinardy Xing <Oracle.RD..._at_gmail.com> wrote:
> On Jun 27, 1:35 pm, sybra..._at_hccnet.nl wrote:
>
> > On Wed, 27 Jun 2007 03:41:31 -0000, Sinardy Xing
>
> > <Oracle.RD..._at_gmail.com> wrote:
> > >Why Oracle allow to log in as sysdba while nothing can be done in the
> > >so call session.
>
> > Incorrect. Shutdown abort in the second session will work.
> > As a charm....
>
> > --
>
> > Sybrand Bakker
> > Senior Oracle DBA
>
> incorrect to the incorrect, please try :)
>
> while shutdown immediate and rolling back in progress you still can
> connect as sysdba using another session but what you can do with it?

shutdown abort. That's what you can do with it. AFAIK nothing more, nothing less

--
Sybrand Bakker
Senior Oracle DBA
Received on Wed Jun 27 2007 - 03:15:18 CDT

Original text of this message

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