Re: Shutdown hangon.

From: spencer <spencerp_at_swbell.net>
Date: Sat, 28 Oct 2000 21:18:01 -0500
Message-ID: <oMLK5.275$n34.133334@nnrp1.sbc.net>

<oratune_at_aol.com> wrote in message news:8tc1ss$jm7$1_at_nnrp1.deja.com...
> In article <39F927F5.C73B32E6_at_cci.de>,
> =?iso-8859-1?Q?J=F6rg=20Br=FCwer?= <bruewerj_at_cci.de> wrote:
> > shutdown immediate rolls back user transactions, but it didn't kill
 user
> > sessions.
> > so it waits still so long, if all user are disconnected. Try this if
 you can:
> >
> > startup the database;
> > login in sqlplus as any user on another task;
> > login as internal on another task and shutdown immediate;
> > -> the task of internal will wait for the user in sqlplus. it
 waits for the
> > time when
> > the user querie a question. if the user did nothing, and stand
 only in the
> > shell of
> > sqlplus, the shutdown process will wait.
> >
> > have fun in this adventure !!
> > joerg
> >
> > David Wang schrieb:
> >
> > > Dear all,
> > >
> > > Yesterday, When I use the command -- shutdown immediate, the
 database is
> > > hangon for more than one hour. The database is very small even
 100MB.
> > > Although I stop it by manually stop the basic service using the
 service icon
> > > in the control pane, I would like to know what is the reason and
 whether it
> > > will be damaged to my database, the following content is abstract
 from the
> > > trace file. Thanks for any responce to help me understand this
 trace file
> > > and the question I metioned,
> > >
> > > "
> > > Dump file D:\orant\RDBMS80\trace\ORA01844.TRC
> > > Thu Oct 26 08:27:59 2000
> > > ORACLE V8.0.5.0.0 - Production vsnsta=0
> > > vsnsql=c vsnxtr=3
> > > Windows NT V5.0, OS V8.147, CPU type 586
> > > Oracle8 Release 8.0.5.0.0 - Production
> > > PL/SQL Release 8.0.5.0.0 - Production
> > > Windows NT V5.0, OS V8.147, CPU type 586
> > > Instance name: orcl
> > >
> > > Redo thread mounted by this instance: 1
> > >
> > > Oracle process number: 17
> > >
> > > pid: 734
> > >
> > > *** SESSION ID:(15.13) 2000.10.26.08.27.58.997
> > > SHUTDOWN: waiting for active calls to complete.
> > > *** 2000.10.26.08.33.02.954
> > > SHUTDOWN: waiting for active calls to complete.
> > > "
> >
> >

>

> Let's go through this again --

>

> SHUTDOWN IMMEDIATE kills all active sessions and rolls back any
> transactions not committed at the time the sessions are killed.

>

> The error message is stating, in ORACLE's cryptic way, that the
> instance is rolling back uncommitted transactions and the shutdown is
> waiting for the rollbacks to complete.

>

> I tend to agree with Howard's post -- avoid SHUTDOWN ABORT like the
> plague, only using it when ABSOLUTELY NECESSARY. I have had to use it
> a few times in my career as a DBA (13 years and counting) but it was
> mostly because orphan processes were consuming valuable resources the
> other users needed [yes, the network was fairly poor on some sites and
> the users would become disconnected due to network timeouts; other
> times the users would inflict this upon themselves by performing the
> dreaded 'Control-Alt-Delete' when they thought their PC was 'hung',
> killing their ORACLE session but not the associated processes]. I have
> also experienced situations similar to Howard's where power lines were
> cut/disabled and there was precious little time to shut the instances
> down in a graceful manner.

>

> I would rather see a database take an hour, or two or three, to shut
> down and then come up in record time than have the database shut down
> quickly then wait for all of the recovery to finish before the users
> can again access the instance.

>

> --
> David Fitzjarrell
> Oracle Certified DBA

>
>

> Sent via Deja.com http://www.deja.com/
> Before you buy.

Yes, let's go through this again...

The "shutdown immediate" statement, issued from svrmgrl (on Oracle 8.0.6 on HP-UX 11.0) does NOT, i repeat, NOT perform pre your description, or per the Oracle documentation.

That is, the database is NOT busy performing rollback, and some user sessions are not disconnected The "shutdown immediate" however, does prevent other users from connecting.

I have tested this under several scenarios. By simply connecting to the database via SQL*Plus on a remote client (and doing nothing else on the client), with no other users connected, the database does not shutdown.

It's grand that you have two or three hours to wait for the database to come down, but for some of us, it is not an option. For example, when the HP-UX system is rebooted, the Oracle processes are always terminated (by the OS) before the shutdown immediate finishes. Recovery, when the database is restarted, rarely takes more than a second or two. Received on Sat Oct 28 2000 - 21:18:01 CDT