|
From: Doychin B. <do...@ds...> - 2009-08-26 15:27:41
|
I can confirm the same problem with FB 2.1.2. It does not happen every time I execute select against mon$statement. Doychin Douglas Tosi wrote: > Hello, > > I'm investigating an obscure bug where a client accessing > mon$statement is receiving an "invalid BLOB ID" error. > This happens only when there are statements submitted by clients using > charset NONE. The charset used by the monitoring attachment does not > matter. The contents of mon$sql_text are not important either. The > error is thrown by the server at the first fetch command. The blob > (mon$sql_text) does not need to be fetched. Simply referencing it in a > where clause also causes the error. > This error happens with Firebird 2.5 beta2 and 2.1.3rc2. It does not > happen with 2.5 beta1, 2.1.1 or 2.1.2. So I'd imagine it has something > to do with recent changes. Tested with 64bit Win7 and 32bit XP SP3. > I'm having a hard time reproducing the issue with a simple test-case. > Are there any known issues that can cause this? > >>From the release notes I can see the following changes as possible > causes. They've all been included in 2.5b2 and 2.1.3rc2. > http://tracker.firebirdsql.org/browse/CORE-2564 > http://tracker.firebirdsql.org/browse/CORE-2482 > > Of course it could be an entirely different cause. Please advise. Any > clues or pointers greatly appreciated. > Thanks in advance, |