Same problem here. I can add that my application is widely deployed, and each instance created a db for its internal configuration. Now everyone of them is failing, so I think it's not a problem of corruption... maybe the start parameters? The jdbc url with which it was created is:
jdbc:h2://amp_db;LOCK_MODE=0;UNDO_LOG=0;TRACE_LEVEL_FILE=0;FILE_LOCK=SOCKET;AUTO_SERVER=TRUE You can find a failing db here: https://www.dropbox.com/s/h0i9ys98dz5xp88/amp_db.h2.zip Opening it with version 1.3.168 will give the error. Please advise here. I can't upgrade if this is not solved somehow... anyhow, thanks for the excellent work you're doing! Germano -- View this message in context: http://h2-database.66688.n3.nabble.com/Unique-index-or-primary-key-violation-SYS-ID-ON-PUBLIC-SYS-ID-23505-168-using-1-3-168-tp4028700p4029077.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.