RE: shutdown abort / startup restrict / shutdown vs. shutdown imm

The Backup & Recovery Handbook has a great treatment of what happens in the various shutdown methods.
Here is a quick summary:
ABORT - Disallow new connections, drop file locks, terminate processes IMMEDIATE - Disallow new connections, terminate current connections and rollback active transactions, flush db block and redo log caches, update file headers, close files, synchronize control files, terminate processes TRANSACTIONAL - Disallow new connections, allow active transactions to complete, terminate current connections, flush db block and redo log caches, update file headers, close files, synchronize control files, terminate processes
NORMAL - Disallow new connections, allow current connections to be completed and sessions logged out, flush db block and redo log caches, update file headers, close files, synchronize control files, terminate processes. Obviously, if the users did not log out of the sessions, the db would not come down.  

If ABORT is used, transactions will be rolled back upon startup (which is why it may take longer to open). In 9i, there was (is?) a known bug where an ABORT would cause the database to not open. Also note that the caches are not flushed. The database will be in an inconsistent state and is not valid for a backup if it is not in archivelog mode (though you may get lucky...).  

-----Original Message-----
Sent: Tuesday, July 23, 2002 12:09 PM
To: Multiple recipients of list ORACLE-L

The differences are
1. shutdown abort - is more drastic, no new users are allowed to log in, disconnects current sessions without rollback, recovery however would have to be done when restarted.
2. shutdown immediate - no new users are allowed to log in, terminating current connections, transactions terminated are rollbacked, recovery would not happen at restart
3. shutdown normal - no new users are allowed to log in, transactions in progress are rollbacked, but would wait for all existing transactions to finish and users to log off, so if a user is logged in when shutdown normal is executed, it would wait forever.  

So shutdown immediate is much quicker and safer. ...Ishrat  

-----Original Message-----
Sent: Monday, July 22, 2002 9:53 PM
To: Multiple recipients of list ORACLE-L

> -----Original Message-----
> From: April Wells [ mailto:awells_at_csedge.com <mailto:awells_at_csedge.com> ]
>
> The solutions (the ones that I got) aren't good ones.
>
> Shutdown abort/startup restricted/ shutdown immediate... (a 'VALID
> solution'???)

This might be a naive question, but why is -> shutdown immediate
better than
-> shutdown abort / startup restrict / shutdown normal ?

(That is assuming of course that no user / job will try to sneak in after you do the startup restrict)

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Fink, Dan
  INET: Dan.Fink_at_mdx.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).