[h2] org.h2.jdbc.jdbcSQLException - unique index or primary key violation: "sys_id on public.sys(id)" 23505-169

Hi All, Can anyone help us in resolving the below issue. The H2 Database file was created with the version 1.3.160 and it is copied and being used in around 1500 local systems. But this db file is being accessed by the Java application with the h2 jar version 1.3.169. There was no problem at all

[h2] Re: org.h2.jdbc.jdbcSQLException - unique index or primary key violation: "sys_id on public.sys(id)" 23505-169

Thanks for your reply Thomas. 1) The DB file was not re-created when upgraded to the higher version from 1.3.160 to 1.3.169. Ideally, It was not noticed that a different higher version of the h2 jar file was getting used in the application than the h2 DB file that was created with the lower versio

[h2] H2 Database corruption : java.lang.RuntimeException: old!=record pos:196012 old:page[196012] data leaf overflow parent:196011 next:0 new:page[196012] data leaf table:10 T10 entries:0 parent:19468

Hi Team, We are getting lot of H2 database corruption cases from clients. Kindly help us to provide some information to address this issue. We tried the Recovery of corrupted DB but we could not recover. Please find below the details of our system. H2 version : *1.3.169* Java version : *1.6.

Re: [h2] H2 Database corruption : java.lang.RuntimeException: old!=record pos:196012 old:page[196012] data leaf overflow parent:196011 next:0 new:page[196012] data leaf table:10 T10 entries:0 parent:1

Hi Kerry, Thanks for the update. Could you please help to update us the root cause behind the MVCC that lead to H2 DB corruption, because number of users affected (80+ users for now) are being increased daily ? Also, what may be the alternate solution to resolve this issue ? Awaiting for your

[h2] H2 Database upgrade

*Hi,* *Kindly help us in understanding/migration h2 from older version to the latest.* *1. h2.db file was created using the version **1.3.161.* *2. Our application connects this h2.db file using the version **1.3.169 and working fine.* *Does it mean the database file has been already upgraded