Subject | Re: [firebird-support] Database corruption issues |
---|---|
Author | Thomas Steinmaurer |
Post date | 2010-10-14T20:36:23Z |
Hi!
http://tracker.firebirdsql.org/browse/CORE-2936
It's marked as fixed in:
V2.0.6
V2.1.4 (not released yet, although snapshots available)
V2.5.0
HTH.
--
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
My blog:
http://blog.upscene.com/thomas/
> We have a client in Australia (we are in New Zealand) who has a largeCore-devs probably jump in here as well, but it might be related to:
> chain of stores. They are periodically getting data base corruption
> messages. They are invariably something along the lines of...
>
> database file appears corrupt()
> wrong page type
> page nnnn is of wrong type (expect 7, found 5)
> gds_$receive failed.
>
>
> Most (almost all) of the errors happen at their head office but they
> also occasionally appear at their shops as well. It shows up in 3
> different databases, some running in FB 2.0 others in 2.1. The
> applications accessing these databases are also all different, so I
> don't think it is being caused by the application. The databases at HO
> run on two different computers. They do have power issues (spikes etc)
> but all machines are (apparently) behind ups devices (with filters).
>
> Usually I can fix the issue with Gfix followed by backup and restore.
> Often (may be always) I have to disable garbage collection (-g) when
> doing the backup for it to successfully complete.
>
> Any suggestion as to what actions to take would be appreciated.
http://tracker.firebirdsql.org/browse/CORE-2936
It's marked as fixed in:
V2.0.6
V2.1.4 (not released yet, although snapshots available)
V2.5.0
HTH.
--
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
My blog:
http://blog.upscene.com/thomas/