Martijn Tonies wrote:

>
> Anyway, I believe this has to do with the operating system locking parts
> of the datafile while copying which means that Firebird cannot write
> in those parts. Obviously, when one part of the file is locked and Firebird
> cannot write to the original file, anything can happen... (but never a good
> thing).
>

I just saw the first report of a message (from a Windows) system that
indicated that a part of the file was locked. I've been reading
Firebird and InterBase support lists for a while, and that error was
news to me, so I doubt it came from a simple copy. A defragmenter, I
would believe, but not that anyone would try to defragment a running
database. Anyway, the result is that the current transaction failed,
but since forced writes keep the database on disk consistent at all
times, the database was still OK - same as if somebody tripped the
breaker to shutdown the server.

Regards,


Ann