| Subject | Re: [firebird-support] Internal Firebird consistency check (cannot find record back version (291) - how to fix and prevent? |
|---|---|
| Author | Alexey Kovyazin |
| Post date | 2014-01-29T11:39:33Z |
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 due to hardware problem in RAM or disk.
>I am trying to fix this error by using gfix: gfix.exe -v -f-user SYSDBA -password masterkey MYDB.FDB
try
gfix -mend ...
gbak -b -g -v -ig ...
And, IBSurgeon FirstAID should be able to export data from this database for sure.
Regards,
Alexey Kovyazin
www.IBSurgeon.com
Hello guys,
I have atleast one database on which this problem occurs when I try to backup the database. I do not know what caused this problem. Is it possible to cause this problem by executing DDL/DML statements?
On this page: "http://ibsurgeon.com/articles/item69" the reason for this problem is explained as: "Most probable reason is wrong transaction management." What is the wrong transaction management? How server could allow this problem to happen?
I am trying to fix this error by using gfix: gfix.exe -v -f -user SYSDBA -password masterkey MYDB.FDB
gfix is returning this:
Summary of validation errors
Number of record level errors : 8
But it does not fix it, everytime I run this command I get the same response from gfix.
I've executed query SELECT COUNT(*) FROM MY_TABLE to scan all records in table and I've got the same message as in backup proccess. So I guess I could manually delete the rows from table? But why gfix does not fix it?
Thanks for your time.