Re: How may idle user sessions be killed prior to a shutdown?

In article: <chubble.2.0052C809_at_pcug.org.au> chubble_at_pcug.org.au (Chris Hubble) writes:
> In article <D6oGH1.FLC_at_bailey.com> mas_at_bailey.com (Mitchell A. Slater) writes:
> >From: mas_at_bailey.com (Mitchell A. Slater)
> >Subject: How may idle user sessions be killed prior to a shutdown?
> >Keywords: shutdown, kill session
> >Date: Fri, 7 Apr 1995 18:24:36 GMT
 

> >I would like to kill all inactive user sessions in my database prior
> >to a shutdown for backup purposes. Alter system kill session
> >indeed kills the session BUT a shutdown normal still waits until
> >something happens on the user side before issuing the Session killed
> >message to the user. I.e, the user has his session killed, but is not
> >officially disconnected until something happens on the client side.
> >This means that if the session is simply idle with no user physically
> >present, that will not happen and the database will not shutdown.
 

> >As an alternate, I've examined doing kill sessions followed by shutdown
> >immediate which seems to do the trick. But I am wondering if just doing
> >a shutdown immediate would yield the same effect? Does the kill session
> >prior to the shutdown immediate buy me any additional graceful rollback
> >and protection of the idle users' data?
 

> >How are others handling this situation?
 

> >I am running Oracle 7.0/7.1 with SQL*Net V.2 under Solaris 2.3 on a Sun
> >Sparc 10.
>
> If you are killing off user sessions, you may as well do a shutdown abort!
> This can be followed by startup then shutdown normal to allow necessary
> rollback. In my experience this is the usual approach prior to system backups.
>
> Chris Hubble...
>

-- 

In preference, don't use SHUTDOWN ABORT since this will require instance recovery
on the next startup - *do* use SHUTDOWN IMMEDIATE which rolls back any incomplete
transactions before completing the shutdown.  Basic order of preference should be
(1) NORMAL - which waits for users to disconnect, (2) IMMEDIATE - which waits for
current call to complete then uses PMON to tidy up users, and last resort only
(3) ABORT which kills the instance with no attempt to clean up.  Remember that if
your database is running with 20Mbyte redo logs, the instance recovery could take
some time!!!

---------------------------------------------------------------------------
| Keith Bremer    EMail kbremer_at_lecky.demon.co.uk                         |
---------------------------------------------------------------------------