Hello,
we are using H2 version 1.4.192. Database URL is jdbc:h2:file:;CIPHER=AES;MV_STORE=false.
The size of the database file is growing dramatically in some environments
and we do not understand why. We checked our code for errors that prevented
committing of Hibernate transactions and the cl
those tables are related to LOB/CLOB/BLOB space management.
it's quite possible we have a leak somewhere in our handling of those,
particularly if you are generating temp tables with LOBs.
Unfortunately, without a test case, it is unlikely that we can fix it.
--
You received this message beca
Thanks Noel for you answer. We will try to track down the code / SQL
statement that causes the growth. What is in your opinion the best approach
to do so?
I was thinking to write some code that monitors the database file size and
logs any size change. I would also log any SQL statement sent to
I did write some code that monitors the database file size. But there seems
to be no clear relationship between insert and delete queries and the size
of the database file. Database file size changes seem to happen very rarely.
Is this because we use hibernate or is it a general behavior of H2?
On 2016/11/24 12:02 PM, Reinhold Bihler wrote:
Another approach would be to monitor the count of entries in the
INFORMATION_SCHEMA.LOBS and INFORMATION_SCHEMA.LOB_MAP.
What do you think? Does this sound more promising?
yes, good idea, If it is a LOB problem, that will point it out fairly q
Is there a fix date and version for this issue? thanks
On Thursday, November 24, 2016 at 4:11:09 AM UTC-6, Noel Grandin wrote:
>
>
>
> On 2016/11/24 12:02 PM, Reinhold Bihler wrote:
> >
> > Another approach would be to monitor the count of entries in the
> INFORMATION_SCHEMA.LOBS and INFORMATIO