Internal consistency check

[Tomasz Dubiel]

Hello.

I've already seen issues when Firebird falsely notified about problem with consistency of the database after running query- is it one of such issues?

I ran query on Firebird 2.5.9 Classic Server on Windows with group by and order by and I got Firebird consistency check:
internal Firebird consistency check (EVL_expr: invalid operation (232), file: evl.cpp line: 1220)

I/O error during "GetFileSize" operation for file "XXXX"
Error while trying to access file

Should be everything ok with the database or backup restore is immediately required?

Best regards.

[alexand...@gmail.com]

Hi!

My suggestion is to do immediate backup/restore, if that is possible at all. If there are errors upon backup/restore then do "gfix mend Firebird" (this Google query will lead to articles about fixing errors). gds consistence check errors are not tolerable, there should be none in the firebird server logs. Backup/restore should be done upon the first appearance of them. At lest that is my 10+ years practice with Firebird. Alex

[alexand...@gmail.com]

Just wanted to add that "gds consistency check" errors are quite an exception - they are not tolerable in any situation. But the remaining other errors (e.g. INET/inet_error: read errno = 10054) are tolerable, they can appear in firebird.log and can be safely ignored. At least it is our practice.

[Tomasz Dubiel]

I know in general, firebird consistency check is message about serious issue with the database, but I would like to know whether in this case this is valid. I saw already cases when running some query produced internal consistency check, but it didnt

make any serious problem, like this:

https://github.com/FirebirdSQL/firebird/issues/5830

I had exactly the same experience. Running query ended with message about Firebird internal consistency check.
Can someone confirm this is the same type of error? In GitHub issue is closed with fix-version Firebird 4.

[Mark Rotteveel]

Although INET/inet_error: read errno = 10054 might be tolerable, it
usually means that your clients are not closing connections correctly.

Mark

--
Mark Rotteveel