Re: shutdown immediate or abort for cold-backup?

On Fri, 17 Aug 2001 11:34:09 +0200, Heinz-Georg Bergerhausen wrote:

>what are your experiences for the shutdown-strategy of an ORACLE
>database for cold backup?
>
>our dba has changed the strategy from
>
>1.) shutdown abort - startup restricted - shutdown immediate
>
>to
>
>2.) shutdown immediate

There is always a risk, when you do a shutdown abort, to be unable to restart the database.

For the shutdown, I use a script that first, do a shutdown immediate. If the database is not shutdown in 10 minutes, It do a shutdown abort (startup restricted, shutdown immediate). So I'm sure that that the database will shutdown in any case and that the shutdown abort will be used only if necessary.

If you backup a database after only a shutdown abort and you have any trouble after the recover, the database will be lost. With a clean shutdown, you will be able to limit the lost. With a shutdown abort, the datafile will be inconsistent. If you can't open the database and play the redolog, the database will be lost. With a clean shutdown, the datafiles are consistents. If you can't open the database, you will be able to reset redolog, drop tablespace ... Received on Sat Aug 18 2001 - 09:45:51 CDT