Forced writes are on. I have not been able to recreate this kind of corruption locally so I don’t know what kind of errors are appearing. The message about corruption comes from a service technician in the field. They usually do have a backup of the database, though, so it’s fortunately not a huge data loss.
Glenn Thomas Hvidsten From: [email protected] [mailto:[email protected]] Sent: 23. september 2015 22:24 To: [email protected] Subject: Re: [firebird-support] Securing database against corruption on systems that suddenly get turned off On Mon, Sep 21, 2015 at 4:53 AM, Glenn Thomas Hvidsten [email protected]<mailto:[email protected]> [firebird-support] <[email protected]<mailto:[email protected]>> wrote: We have FirebirdSQL (2.1) running on a client computer (Windows). This client has some problems with his power grid which causes the PC to suddenly and unexpectedly shut down in infrequent intervals (usually once or twice per day). Most of the time this doesn’t cause any problems, but once in a while this causes the database to be corrupted. I’m not at all surprised that the database gets corrupted like this (as turning off a computer without shutting everything down gracefully can have that effect). If you have turned off forced writes, corruption is likely. If forced write is on, what are the errors you're seeing when the database is corrupted? I'm not suggesting that you disregard advice about adding a UPS and make backups - excellent suggestions - but the Firebird architecture should survive a power failure if writes are being forced to disk in the correct order. So I'm curious... Good luck, Ann **************************************************************************** Denne epost har blitt kontrollert for virus av Comendo Norge AS This e-mail has been scanned for viruses by http://www.comendo.no **************************************************************************** [Non-text portions of this message have been removed]
