Hi,
we experienced a database corruption that ended up with tons of errors.
This happend when trying to backup the database:
gbak:@ records written
ghak: writing data for table ST$_BLE_EWI_VAT_DTPN
gbak:@ records written
gbak: writing data for table ST$_ANL_ST_ZA_SPRZ_RS5
gbak:@ records written
ghak: writing data for table ST$_HM_ZAPIS_POZ_ZAMODB
gbak:@ records written
ghak: writing data for table ST$_SS_STATUS_KONT
gbak:@ records written
ghak: writing data for table ST$_XXX_LISTA_ZADAN
gbak:@ records written
gbak: writing data for table ST$_POTW_ZAM
gbak:@ records written
gbak: writing index PK_KSEF_FRMSNAGL_MSCSPRZ
gbak: writing index FK_KSEF_FRMSNAGL_MSCSPRZ_MSC
gbak: writing index FK_KSEF_FRMSNAGL_MSCSPRZ_FRMS
gbak: writing index FK_KSEF_FRMSNAGL_MSCSPRZ_DEFDOK
ghak: writing index MK_KSEF_FRMSNAGL_MSCSPRZ
ghak: writing data for table KSEF_FRMSNAGL_MSCSPRZ
gbak:@ records written
ghak: ERROR:database file appears corrupt (/backup/reczny/awaria 28.04.2026/INERGIA.gdb)
gbak: ERROR: wrong page type
gbak: ERROR: page 3207004 is of wrong type (expected index root, found index B-tree)
gbak: ERROR:gds_$compile_request failed
gbak:Exiting before completion due to errors
We suspect the correlation with this "Error at disconnect", as it froze the firebird.
Firebird couldn't accept new connections, only option was to restart the firebird service. After that the backup was not possible as shown above.
baza_pcb Mon Apr 27 10:55:52 2026
Database: /home/firebird/DB.gdb
Error at disconnect:
deadlock
update conflicts with concurrent update
concurrent transaction nusber is 12692299
At trigger 'ST_ATTACHMENTS OD" line: 5, col: 3
The gfix -v -fu result:
Summary of validation errors
Number of record level errors : 1612
Number of index page errors: 22
Number of pointer page errors : 1
Number of pointer page warnings : 78
Number of database page warnings : 8
The firebird.log has lots of "Record x has bad transaction x in table x":
baza_pcb Wed Apr 29 10:40:38 2026
Database: /backup/reczny/awaria 28.04.2026/DBgdb
Error: Record 431068 has bad transaction 13130906 in table DOKUMENT (172)
The errors are occur on different tables. What does this error mean exactly? Is it repairable in any way?
Best regards,
Marcel