Re: Shutdown Abort - Not a Good Idea, Right?

In general you should not shutdown abort, and in the 7 years of Oracle DBAing (v6.0 -> v8.0) I have only come across one database that could not be started following a shutdown abort.

However, the time taken by Oracle to shutdown immediate a database is sometimes considered excessive, especially if there is a large transaction currently active and needing to be aborted. Having said this though, Oracle will recover this transaction during you startup process, so all you are doing is delaying the inevitable crash recovery. Also, if you are in Archive Log mode, the shutdown normal must wait for the Archive to be completed, because the new log file is opened enabling the previous one to be archived.

Hope this helps,
Andrew

"M. Bhatti" wrote:

> I just recently noticed that, before doing cold backups, our db
> instances (Oracle 7.3.2/8.0.5, Sun Solaris 2.5.1) are shutdown aborted
> than brought up and shutdown normal, so that the cold backup can be
> started immediately after the shutdown normal.
>
> Question is, I thought shutdown abort should not be used except in
> extreme conditions ie when a db instance
> cannot be shutdown normal/immediate.
>
> So, I assume that:
> This is bad idea right (shutdown abort)?
> What can happen to the db?
>
> Thanks for any input.
>
> mkb
Received on Wed Apr 21 1999 - 10:47:45 CDT