I'm also having issues with h2 1.4.92 where the database will grow every
time a LOB is saved. The workaround is to do the RUNSCRIPT command but I'm
getting this error when trying to reimport:
RUNSCRIPT FROM 'D:\tmp\toolkit.sql';
Table "SYSTEM_LOB_STREAM" already exists; SQL statement:
Hi,
This last time there was also an index corruption, so we could not do a
> dump and restore.
>
Hm, you should still be able to use "script to...". Did this not work?
>
> Do you have any suggestions on how to investigate the cause of this? E.g.
> I have seen some threads mentioning the Recover
Hi list,
We have a particular client where the H2 database grows from time to time
until 50-60 GB, where it is supposed to be 3-4 GB. We are using
version 1.4.191 with pagestore. It might be related to the inserted data,
because the client has had it on two machines.
We have 'reset' the db sev
