Hello,

we recently had two customers with corrupted databases after
power-outages. As it turned out, our database had forced writes
disabled. (I don't know why or how this happened, but we'll fix that
in future updates)
However, because the databases were corrupt, we had to try to fix
them. Because we never had a corrupted database before (working with
Firebird for more than 7 years now with many small to large
installations), I was inexperienced with fixing Firebird's
database-files.
I wrote up a blog-post about recovering a database, but I'm not 100%
certain that every detail is correct and it's the best way I am
describing. So I'd be glad if someone experienced could do a short
proof-reading of the post. (Any remarks and corrections should be sent
to the mailing-list so that the Firebird-community can benefit from
it)

Here's the post:
http://daniel-albuschat.blogspot.com/2009/12/firebird-database-corruption-and-what.html

I'm especially interested in:
- Are there more reasons for a database-file to get corrupted?
- What exactly does gfix do using the -f -v and the -mend parameters?
- Is there more than enabling Forced Writes to make a database robust
against power-outages, etc.?

Thanks!

Daniel Albuschat

--
eat(this); // delicious suicide