Hi,

> I cannot say to you the exact value -I am not now where the
> problematic BD is- but this morning I took a look at the statistics,
> and I saw a value around 2000 in 'Oldest transaction, 'Oldest
> active', 'Oldest snapshot' and 'Next transaction'. I realized it was
> quite big, but I didn't know if those values where normal or not.

The difference needs to be as small as possible. Large gaps
between those numbers can cause garbage to build up, thus
causing database growth.

> If you could give me some advise with this information, perfect, if
> not, as soon as I could get the actual gstat information I will post
> it.
>
> In any case, if, as you say, the transactions are messed up, what can
> be done to fix them. This morning I have gbak and gfix the BD but it
> seems it didn't solve the problem.

Keep your transactions as short as possible. Do a COMMIT and
not COMMIT RETAINING.

Do you have long transactions open for reading data?

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com