Hi,

Sorry for the delay!

> Reading this thread, I'm a bit confused about whether there's an
> existing error in the bit handling logic or not.

No. The problem was only bad performance.

> Starting from an empty database, I loaded approximately 2GB of data,
> and closed the database.  I think this load appeared to be successful
> (that is, I don't think it threw any exceptions).
>
> The next time I tried to connect to the database, however, I received
> this error:

Can you reproduce this? I would be really interested in having a
reproducible test case! Even if it's only reproducible sometimes.

> 12-05 15:29:35 database: error initializing summary for C:\ProgramData
> \Company\Product\cache\h2\productDB.data.db size:3437000 stage:1
> java.lang.RuntimeException: Redo failure, block: 512 expected in-use
> bit: false

Most likely you can open the database if you append ;RECOVER=1 to the
database URL. However I have some questions:

- What is your database URL?
- Did you use multiple connections?
- Do you use any settings or special features (for example, the setting LOG=0,
  or two phase commit, linked tables, cache settings)?
- Is the application multi-threaded?
- What operating system, file system, and virtual machine
  (java -version) do you use?
- Is the database usually closed normally, or is process terminated forcefully
  or the computer switched off?
- Is it possible to reproduce this problem using a fresh database
  (sometimes, or always)?
- Are there any other exceptions (maybe in the .trace.db file)?
  Could you send them please?
- Do you still have any .trace.db files, and if yes could you send them?

Regards,
Thomas

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to