Make sure that your client and server jars use the same version.
Difference in those versions caused for me corruptions before.
At least all of the clients that update data should have the same version, I think.

- Rami

On 25.4.2019 16.28, Silvio wrote:
Hello all,

Since our upgrade to h2-1.4.199 we are experiencing frequent database corruptions. I reported this earlier and have seen at least one similar report from someone else in this group showing an almost identical error. There has been no response since.

Is there any reason to assume 1.99 could be more susceptible to some kinds of database corruptions than, say, 196 which is the version we where using before the upgrade? If so, is this something someone is looking in to? Can we take special measures to prevent corruptions or at least reduce the chance they occur?

More specifically: is it still safe to simply close all connections to a DB, wait a couple of seconds and then copy/backup the database files at the file system level? Is it still safe to shutdown a (Linux) process that may have active database connections and may even be writing to that database (not SIGKILL but a plain SIGTERM)? If not: what can we do to securely copy a database at file system level or shut-down/restart a running application?

Our problems are making us consider reverting to 196 but that seems backward. Please advice.
--
You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Reply via email to