> It looks like you have stumbled on the same bug as some others on
> this group. You should read these previous threads for some
> background. What machine do you have? and are you using Classic or
> Superserver?
>
> FB 1.5 - Continuing database corruption issues
> http://tech.groups.yahoo.com/group/firebird-support/message/81090
>
> Corruption in Firebird Classic 1.5.3.4870
> http://tech.groups.yahoo.com/group/firebird-support/message/81723
>
>
> Do you still have a copy of the original corrupted database before
> running Gfix -mend on it? If so would you be willing to send it to Ann
> Harrison as requested in this message :-
>
> http://tech.groups.yahoo.com/group/firebird-support/message/81876
>
> In terms of fixing the database there have been a few solutions
> suggested in the threads I mentioned above but I will detail the
> solution that works for me.
>
> Sometimes you dont need to run gfix -mend so first try :
>
> 1.) Make a copy of the corrupt database!
> 2.) gbak.exe -B -V -ig -G
> 3.) Restore as normal.
>
> If that fails then try :
>
> 1.) Make a copy of the corrupt database!
> 2.) gfix -mend
> 3.) gbak.exe -B -V -ig -G
> 4.) Restore as normal.

Whenever we are talking about database corruption, one should also check
if the installed RAM is faulty. A tool like memtest could help here.

Wrong record length and wrong page type errors and getting different
results when running gfix -mend several times, might be indicators to a
faulty RAM.


Just a thought.



--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com