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 version. 2) My concern is all about, if there, such a problem due to the conflict of version, why all DBs have not thrown this exception where as only few? 3) DB URL is: jdbc:h2:<H2_DB_File_Path_with_file_name_excluding_.h2.db>;CIPHER=AES;MVCC=TRUE;AUTO_SERVER=TRUE 4) Yes, Before any update through the application, a H2 DB back-up will be taken.
-- View this message in context: http://h2-database.66688.n3.nabble.com/org-h2-jdbc-jdbcSQLException-unique-index-or-primary-key-violation-sys-id-on-public-sys-id-23505-169-tp4029704p4029720.html Sent from the H2 Database mailing list archive at Nabble.com. -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
