Re: shutdown -- big transaction

From: Jeremiah Wilton <jeremiah_at_wolfenet.com>
Date: Tue, 05 Oct 1999 16:06:45 -0700
Message-ID: <37FA8485.18232F18@wolfenet.com>

Greg Stark wrote:

> So what exactly is the consequence of shutdown abort? We're always impatient
> to shut down the database as quickly as possible and often give up and
> shutdown abort. If what you're saying is true there's little consequence, why
> doesn't shutdown always do the equivalent of abort?

In certain cases, such as cold backups and version upgrades, the datafiles have to be consistent to the same SCN. For most other purposes, shutdown abort should be perfectly fine. It will even reduce downtime because you don't have to wait for transaction rollback.

> I've also been told that after an abort i should start the database up and do
> a clean shutdown and then start it up again before going live again. Is that
> just superstition?

There is no reason to do that unless there is a compelling need for consistent datafiles, such as a cold backup or version upgrade. --
Jeremiah Received on Tue Oct 05 1999 - 18:06:45 CDT