> This is followed by 'GDS Exception. 335544726. Error reading data from
> the connection.' as the FB process on the server has been killed.
> Once this happens the database is effectively unusable by our

application.

This error message means that the server process has crashed. It does
not necessarily mean the database is corrupt, a faulty UDF will cause
the same error. Judging from your other post, if it happens during the
same query, then look for any UDF involved (including those sitting in
triggers fired by your query). Of course database corruption will also
cause the server process to crash when it attempts to read it, but
normally you get some hint by other error messages (wrong record
length etc). The message you talk about can be easily duplicated by
restarting the firebird service after you have made a connection.

>
> Currently we are running the 1.5.1 Classic server installer and
> connecting using Jaybird 1.5.5.
> All our Macs are running at least OSX 10.3.4.
>
> We have not seen this problem on any of our Windows sites running
> 1.5.2 SuperServer.
>
> In some cases doing a backup and restore seems to get the database
> running again but in other cases not.
> We have one client datafile here that exhibits this problem. gfix
> reports that there is one error but when it is told to repair it just
> gives a segmentation fault.
>
> Unfortunately this is happening randomly at some sites so it isn't
> something that we can easily replicate. These are 'live' sites so it's
> not a good situation.
>
> Is this familiar to anyone?

I am not familiar with the Mac builds, and whether there are any
stability issues of note, but certainly you have had to port any UDF
you make use of. Try and create a test case to duplicate it.

In 300 sites, we have seen database corruption twice in 2 years, so I
find your experience unusual. One corruption was easily fixed with
gfix, the other required a data pump.

Adam