I also don't understand why there is no sweep interval showing for the corrupted file.
Just need to make sure since I don't understand why these high numbers went back down after using gfix on the corrupted file. I read the manual but I doubt the corruption is related.
Variable header fbstat -h /home/firebird/my_db.fdb_fixedĭatabase "/home/firebird/my_db.fdb_corrupted_fixed"Īctual question: is there a potential link between the corruption of the database and the high numbers in the statistics above? fbstat -h /home/firebird/my_db.fdb_corruptedĭatabase "/home/firebird/my_db.fdb_corrupted" Here are fbstat output for the corrupted file, and below for the fixed file. I also guess not having a sweep interval in the corrupted version is part of the problem? I assume this normal, but I'd like to know if it's normal to have these numbers increase all the time. The statement executed before the error was an insert or update, but I do a lot of those (in small batches) before doing a commit that I make sure to do each time.Īfter fixing it with gfix, I noticed that the transaction count (and Generation) values got reset down. 659 is of wrong type (expected 7, found 109)\n- internalįirebird consistency check (error during savepoint backout (290),įile: exe.cpp line: 4056)', -902, 335544335) 'Error while executing SQL statement:\n- SQLCODE: -902\n- databaseįile appears corrupt (/home/firebird/my_db.fdb)\n- wrong page type\n. My firebird SQL database got corrupted recently, and I'm not sure why.
0 kommentar(er)
