--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:

> > Hello
> >
> > I am evaluating databases for a particular application. One of the
> > most important requirements is that the database survive a "power plug
> > pull" during use without database corruption. So far, Firebird fails
> > this requirement. Are there any settings that can minimize this kind
> > of corruption problem?
> >
> > Ian
> >
>
> this would only (likely) happen on a windows box with forced writes

set to

> off.
> Ensure that forced writes for the database (not server) are set to

ON in all

> OS environments and corruption is unlikely.
> (nothing will protect against lightneing strike power surges to that fry
> your hard disk though)
> Alan

Hi Alan

Thanks for your suggestion. I added the following line to my
firebird.conf file:

ForcedWrites=On

But after 4 powerdowns during insert activity, I got the following
message after trying to update a database table:

... update agt_idle set end_idle='2005-03-01 07:50:51' where
guid='agent67890123026' and end_idle is null
SQLCODE: -902
firebird reports: internal gds software consistency check (cannot find
record back version (291))

By the way, this is on a realtime variant of Linux, Carrier Grade Linux.

Ian