> On Fri, Sep 11, 2009 at 10:08 AM, Vlad Khorsun
> <hvlad@...> wrote:
> > > It's quite reproducible moving from 2.1.2 to 2.1.3
> > Then create reproducible test case and register it in the tracker.
>
> Vlad, do you have access to a windows machine where you could install
> sinatica monitor? I've been trying to reproduce this error with a
> simple test-case for a week now and nothing. OTOH the error is very
> easy to reproduce using sinatica monitor.
> 0) Use Firebird 2.1.3 or 2.5 beta 2
> 1) use isql to attach to a database using NONE charset.
> 2) run any statement and do not commit.
> 3) register database with sinatica monitor and start monitoring.
>
> Please let me know if I can help in any way.
>
> Thank you,
> --
> Douglas Tosi
> www.sinatica.com

I think the key, here, is that the subsequent connection (sinatica in this
case) is making an immediate read of the mon tables. try any second
attachment which reads the mon tables. Any second attachment with NONE which
doe not try to read the MON tables does not raise this exception.
Alan