On Thu, 2003-07-10 at 00:50, Yang Jin wrote:

> Ann Harrison <aharrison@...> wrote:
> Carlos H. Cantu wrote:
>
> > I run a
> >discussion list with lots of users (all portuguese speakers) and many
> >of them has or had problems with db corruption sometime. They asked me
> >to put this poll online so we could have an idea of what is the
> >scenery where db corruption is more likely to happen.
> >
> >
> Almost all the problems I've seen from Brazil are databases that were
> running with forced writes off on windows when the power failed. Hard
> to blame the database for that.
>
> Cheers,
>
>
> Ann
>
>
> I agree with the view that loss power make database corrupt.But I think It is most important to solve the problem by user when the database corrupt.
>
> How to restore the normal by user so that they can continual use the application?
>
> A tool is need to use by user to restore the corrupt database.Let's make it.
>

I think your trying to cure the symptom rather then the disease. The
symptom is database corruption, the disease is Windows with forced
writes OFF upon power failure. I see three solutions without new tools
being needed:

1) Run Firebird on Windows with Forced Writes ON
2) Run Firebird on another Operating System that writes the cache to
disk more efficiently, i.e. Linux/Unix.
3) Make sure that power failures don't affect operation. For example a
UPS with power failure detection, that shuts the server down when the
power fails.

Paul S.