Re: [h2] H2 corrupted DB

> > We do actually make a copy of the file, but we call SET EXCLUSIVE 1 before > we do that. It does not matter, such copy may still be unusable. Database can write something in background and copy can read inconsistent older and newer data. If you really want to copy the file, you need to

Re: [h2] H2 corrupted DB

@Thomas Mueller - You mentioned that file corruption may take place if "copy the database file while it is in use, without using the online backup command". Can you please elaborate? Do note that we do make a file copy while DB is in use, but we make a call to "SET EXCLUSIVE 1" before. What

Re: [h2] H2 Corrupted DB

I agree, I don't see anything obvious in that log. You could try checking the H2 .trace.log file which lives next to the DB file, sometimes that manages to capture exceptions that the application ignores. interrupt() closes the NIO FileChannel object, which means the whole DB is effectively

Re: [h2] H2 Corrupted DB

Update: I connected to the DB via the H2 console without issues and executed the SQL statement from the exception and it finished successfully. Maybe the issue is in jira. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from

Re: [h2] H2 Corrupted DB

Hi The root exception there is "ClosedChannelException", which means one of two things (1) something else happened before this exception, and we'd need to see that earlier exception to know what the problem was (2) something else called interrupt() on that thread, which is very very bad

[h2] H2 Corrupted DB

Hello! I stumbled across an error that should have been fixed according to [1]. The issue happens during import of quite big jira backup. (Unfortunately I cannot send you the database as it's quite big and contains confidential data) Here is the issue: 2016-04-11 15:33:11,774

Re: [h2] H2 corrupted DB

Hi, I have the same problem with version 1.4.190, any suggestion? 在 2015年10月15日星期四 UTC+8下午11:50:09，Thomas Mueller写道： > > Hi, > > FYI this problem is fixed since version 1.4.188. The problem was that if > writes were re-ordered, and a power failure occurred, truncate was > sometimes done before

Re: [h2] H2 corrupted DB

Hi, FYI this problem is fixed since version 1.4.188. The problem was that if writes were re-ordered, and a power failure occurred, truncate was sometimes done before a previous write. Regards, Thomas On Tuesday, May 5, 2015, Osvaldas Ziukas wrote: > > > 2015 m.

Re: [h2] H2 corrupted DB

2015 m. gegužė 5 d., antradienis 08:45:59 UTC+3, Thomas Mueller rašė: Hi, That's strange. The last part of the file is missing. Looking at the H2 source code, the file truncate code is very simple and conservative (MVStore.shrinkFileIfPossible, which is calling getFileLengthInUse). It

Re: [h2] H2 corrupted DB

Hi, That's strange. The last part of the file is missing. Looking at the H2 source code, the file truncate code is very simple and conservative (MVStore.shrinkFileIfPossible, which is calling getFileLengthInUse). It looks unlikely that there is a bug in this area. Could you describe what you

[h2] H2 corrupted DB

This happend with newest H2 version i got and updated programs. h2-1.4.187.jar In 3 Days i renewed ~200 client programs, same happend to at least 5 04-28 16:53:35 database: flush org.h2.message.DbException: General error: java.lang.IllegalStateException: Reading from

Re: [h2] H2 corrupted DB

Hi, The database is trying to read past the end of the file... Would it be possible to send me the database file to investigate? Regards, Thomas On Wednesday, April 29, 2015, Osvaldas Ziukas osvaldas.ziu...@gmail.com wrote: This happend with newest H2 version i got and updated programs.