Hi Nando,

Some good news and some bad news :-)

The Good News: I can reproduce the problem as now described - by
attempting to connect with Forced Writes turned on.

IMPORTANT: I also get the same error with IBConsole - but you have to
ask for the database properties to see it. (Whereas IBO is doing an
automatic retrieve of properties as part of the connect process, so
you see the problem earlier.)

So no the problem is not IBO specific, and no it is not related to
buffer sizes when retrieving database_info.

The Bad News: I dont know what the problem is. However if you asked
me to guess I would say it related to the change in the engine which
defaults forced writes back to true. (But that is just a guess, I
have not been part of the FB development.)

The difference in the engine, and the fact that the forced writes
status is stored in the database, could explain why backup/restore
resolves the problem - presumably synchronising the stored value with
the expected value.

I see the topic has now been raised in IB_Support, where I think this
topic now belongs. Hopefully someone there will indicate what they
think of the problem.

In the short term I suggest working with forced writes turned off, or
reverting to the previous FB release (it was still better than IB6).

Geoff Worboys
Telesis Computing