Subject | invalid block type encountered (147) |
---|---|
Author | Rolf Bredemeier |
Post date | 2011-06-21T08:14:22Z |
Hi all,
in Firebird 2.5.0 is a bug:
http://firebird.1100200.n4.nabble.com/FB-Tracker-Created-CORE-3389-isc-dsql-exec-immed2-with-zer
o-transaction-handle-could-lead-to-a-BUGCH-td3382984.html
In short: caused by an invalid transaction handle.
Before i updated to IBO v.4.9.14 i never had any trouble with this bug.
But now, our server recently chrashes with log entry:
internal Firebird consistency check (invalid block type encountered (147), file: exe.cpp line:
1010)
I could not figure out why. a little indication my be following scenario:
- open a query
- fetch records
- while processing data, an error occurs, for example divide by zero
- the query is NOT closed (missing try-except block in my application)
- then application shows error window, the user click ok and continue with work
- then the same query is used in an other procedure:
- qry.close
- qry.sql.text='...'
- qry.open ---> crash!
But i'am not sure. It's hard to simulate.
The only way to fix was an update to firebird 2.5.1. in this version, the bug CORE-3389 is
fixed.
With that update, no errors anymore.
Is there someone with similar effects?
It there a way, to check before executiong a query for valid transaction handle?
Best regards,
Rolf from germany
in Firebird 2.5.0 is a bug:
http://firebird.1100200.n4.nabble.com/FB-Tracker-Created-CORE-3389-isc-dsql-exec-immed2-with-zer
o-transaction-handle-could-lead-to-a-BUGCH-td3382984.html
In short: caused by an invalid transaction handle.
Before i updated to IBO v.4.9.14 i never had any trouble with this bug.
But now, our server recently chrashes with log entry:
internal Firebird consistency check (invalid block type encountered (147), file: exe.cpp line:
1010)
I could not figure out why. a little indication my be following scenario:
- open a query
- fetch records
- while processing data, an error occurs, for example divide by zero
- the query is NOT closed (missing try-except block in my application)
- then application shows error window, the user click ok and continue with work
- then the same query is used in an other procedure:
- qry.close
- qry.sql.text='...'
- qry.open ---> crash!
But i'am not sure. It's hard to simulate.
The only way to fix was an update to firebird 2.5.1. in this version, the bug CORE-3389 is
fixed.
With that update, no errors anymore.
Is there someone with similar effects?
It there a way, to check before executiong a query for valid transaction handle?
Best regards,
Rolf from germany