Thank you, Paul.
There were issues related to RAM and while attempting to upgrade RAM (and
OS from 32 to 64 Bit) I lost the corrupted database.
Regards,
Rajiv
On 13 Jun 2017 2:03 pm, "'Paul Beach' pabe...@waitrose.com
[firebird-support]" wrote:
<<1. I got
Hi Alexey,
Thanks for your quick help. I think RAM is the issue.
Regards,
Rajiv
On 10 Jun 2017 1:44 pm, "Alexey Kovyazin a...@ib-aid.com [firebird-support]" <
firebird-support@yahoogroups.com> wrote:
Hi,
Usually such corruptions happen due to hardware problems.
Check you RAM
Hi,
Usually such corruptions happen due to hardware problems.
Check you RAM
https://ib-aid.com/en/articles/how-to-check-ram-and-avoid-database-corruptions/
Try to fix with standard means
https://ib-aid.com/en/articles/how-to-repair-a-corrupt-firebird-database/
If it fails, FirstAID will help.
Try 3.0.2, probably another situation related to
http://tracker.firebirdsql.org/browse/CORE-5392
Slavek
Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
Hi
I am no expert in these things but I thought that DB file access that
was not 'through' the FB server while FB server is running could cause
DB file corruption. With our systems we always exclude the FDB from
virus scanning and external backup applications. We have a FB backup
(GBak) run
Hi Ian,
It seems that you have multi-volume database, is it correct?
Regards,
Alexey Kovyazin
IBSurgeon
Hi FB Support!
We have been running FB since IB4.2 days and have only previously had
any database corruption when we've had hardware issues...until
recently, when I've seen this error
Hi,
The nature of errors is the following - one of record's backversions is
missing, and Firebird cannot read chain of back versions to build actual
(yours) version of this record.
The reason wrong transaction management, I think, is not correct, and
we will change it - usually this happens