On Wed, 2 Apr 2003, GovindanK wrote: > Shutdown immediate does rollback and will take time if no.of users > is high.
Number of users is not the largest contributing factor to shutdown immediate taking a long time. The longest poles in the tent are large transaction rollback and lazy temp segment deallocation. > On the otherside, shutdown abort simply takes the db down and does > not bother about anything else. As per manual, if you do a shutdown > abort then you WILL need the online redo logs for recovery just in > case. Do you know of anyone who does not have their online redologs? You pretty much need them or your database would have crashed a long time ago. > Think twice if your db is in NOARCHIVELOG mode. If your db is in > ARCHIVE mode make sure the logs are multiplexed. As has been pointed out, having multiplexed logs has nothing to do with archivelog mode. Furthermore there is no reason to be more careful about using abort if you are in noarchivelog mode. Crash recovery will not need any archived redologs, since it only needs those logs since the last checkpoint. -- Jeremiah Wilton http://www.speakeasy.net/~jwilton -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Jeremiah Wilton INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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).
