[199] in Athena_Backup_System
Re: "cleanly"
daemon@ATHENA.MIT.EDU (Diane Delgado)
Fri Feb 23 09:01:20 1996
To: athena-backup@MIT.EDU
In-Reply-To: Your message of "Thu, 22 Feb 1996 19:36:00 EST."
<9602230036.AA25509@partly-cloudy.MIT.EDU>
Date: Fri, 23 Feb 1996 09:00:53 EST
From: Diane Delgado <delgado@MIT.EDU>
>- It is *NOT* acceptable that the DB become available for use
> (e.g. after a reboot) while its consistency is still in doubt (i.e.
> before some sort of consistency checker is run).
As usual, I'd like more information on what the "consistency checker"
is supposed to be. Is it sufficient to use the Oracle tools which
effect a roll forward / roll backward to a consistent state or
is this some tool that we need to write which is specific to the
ABS tables and data?
By the way, the DB's availability after such situations is strictly
up to the adiminstrators (this is a policy issue) and shouldn't
be listed as a requirement. I certainly wouldn't object to
restating this requirement as: "There must be a means available to
verify/ensure that the DB is in a consistent state while it is
closed/offline ".
