Hi,
I work for a small company using (the latest stable) H2 in our software.
Our client base is starting to grow (+-100 installations on client
computers, most have DB's multiple GBs in size) and we are starting to run
into more problems with broken (and sometimes worse: unrepairable) H2 DBs.
;mv_store=false" in the
> database URL). Whether you use the very latest 1.4.x version or 1.3.176
> will probably not make a big difference.
>
> I would consider creating online backups regularly, but I'm not sure if
> that's feasible in your case.
>
> Regards,
Hi Thomas and list,
2015-07-03 Thomas Mueller :
>> Is there any way to know for sure a database is consistent?
>
> The statement "script to " will detect most corruptions. It will
> not detect corruptions in just the secondary indexes, but those are quite
> rare.
It appears it doesn't detect the
Hi Thomas and list,
After investigating another corruption yesterday, we noticed something
strange: a few minutes before the DB was found corrupt there was a Volume
Shadow Copy created for the drive where our H2 files are located.
Apparantly there are multiple reports on the internet that suspect
Hi Thomas,
Any news on a new version for PageLog that includes a fix for this?
Regards,
Rob.
Op dinsdag 7 juli 2015 17:59:46 UTC+2 schreef Thomas Mueller:
>
> Hi,
>
> I see, this could be the problem. I'm still working on a file system
> implementation that reorders writes (I was on vacation fo
Hi list,
When inserting a large file (+40 MB) into a BLOB column using the H2 server
mode we get a connection reset on the second or third file (this appears to
be random) within our application. This connection reset results from a
protocol error on the server side traced back to TcpServerThre
I forgot to mention:
We also made sure there is only one thread accessing the JDBC connection
from our application.
Thanx for any hints on how to investigate this further.
Regards,
Rob.
Op vrijdag 15 april 2016 15:39:11 UTC+2 schreef Rob Van Dyck:
>
> Hi list,
>
> When inserting
Op zaterdag 16 april 2016 20:59:58 UTC+2 schreef Noel Grandin:
>
> What I would suggest is that you try running the latest 1.4 release with
> the old engine i.e. with ";MV_STORE=FALSE" in your URL, and see if the
> problem is still there. If it is, I will try to reproduce it.
>
Thanx Noel. That
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
