Thanks for your help. It appears the nightly backup may be the culprit. Regarding the file extension, can you elaborate on the risk of having the .gdb extension?

I believe the installation is classic, ( I was not aware the choice existed at that version.)

Thanks again

Scott Breidenbach
Working Systems
218 1/2 W. Fourth Street
Olympia WA 98506
360-943-7640 x104

________________________________

From: firebird-support@yahoogroups.com on behalf of Dimitry Sibiryakov
Sent: Wed 8/5/2009 12:29 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Repeated database corruption

> The client is currently using Firebird version 1.52.

Superserver or classic?

> In the most recent occurence, the first sign of something wrong according to the log file was this:
>
> FS2 (Server) Tue Jul 21 00:19:47 2009
> Database: D:\LABORPOWER\DATA\LPIBEW25.GDB
> I/O error for file "D:\LABORPOWER\DATA\LPIBEW25.GDB"
> Error while trying to read from file
> The process cannot access the file because another process has locked a
> portion of the file.
> internal gds software consistency check (error during savepoint backout
> (290))

I would recommend to change DB file extension ASAP.

> 1) We recently found out that the client was doing a nightly tape backup which includes the .gdb database file.
> Could this be causing any the problems?

Yes, backup process do exactly what is written above - lock portion
of file. The same can do an anti-virus.

SY, SD.


------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Visit http://www.firebirdsql.org <http://www.firebirdsql.org/> and click the Resources item
on the main (top) menu. Try Knowledgebase and FAQ links !

Also search the knowledgebases at http://www.ibphoenix.com <http://www.ibphoenix.com/>

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Yahoo! Groups Links







[Non-text portions of this message have been removed]