Re: shutdown -- big transaction

Brian Peasland wrote:

> A "shutdown abort" does not flush the db buffer and redo log caches. It
> does not update file headers. It does not synchronize control files and
> db files. It's not a good way to bring down the database. While most
> times you can get away with doing an abort, you are taking a big risk
> with your data.

Exactly what kind of damage do you think a database will incur as a result of shutdown abort? Keep in mind that:
1) All dirty buffers are written to disk whenever a chekpoint occurs. 2) All committed changes since the last checkpoint are in the redologs (That's one of the requirements of a commit - it won't return until the log buffer is flushed).

Therefore there is nothing wrong with shutdown abort unless you genuinely need consistent datafiles (like for a cold backup or upgrade). Even for those, you can shutdown abort, startup restrict, shutdown immediate.

For quick restarts on a huge heavily accessed system, shutdown abort is a godsend. Compare a 15-minute shutdown immediate/startup with a 25 second shutdown abort/startup.

--
Jeremiah Received on Fri Oct 08 1999 - 17:56:35 CDT