Hi ViK,

It's probably easier to use a different thread, otherwise things are
easily mixed up.

You are using version 1.2.132 from 2010-03-21 (the error code
[90030-132] contains the build number).

I'm not sure what the problem could be, but it doesn't look like a bug
in the database to me.
For each write operation, the checksum is updated in one central place,
and I don't know a case where a bug in the database engine ever caused
a wrong checksum.
I also don't think the soft LRU cache could cause this problem.

There were bugs that could cause a corrupt database, but they are not
related to a wrong checksum:

Version 1.2.143 (2010-09-18):
In some cases (specially when using a small cache size or a large
database over 1 GB) for some operations like ALTER TABLE the data was
written before the transaction log entries, which could cause a
corrupt database if the process was killed during the ALTER TABLE
operation. Thanks a lot to Victor Pyankov for helping solve this
problem!

Version 1.2.137 (2010-06-06):
The changes that were made to support large transactions also fixed a
bug with large transactions (when the undo log file size is larger
than 2 GB).

Version 1.2.135 (2010-05-08):
When killing the process while the database was writing a checkpoint,
while it was closing, or while running recovery (while removing
temporary tables from a previous run), the database could become
corrupt. A new test case has been implemented to ensure such problems
can not occur in the future.

To get a wrong checksum, I could think of the following reasons:

- A bad disk (I would run some diagnostics).

- Another application concurrently writing to the same file. I know a
case where a backup was restored (over the database file) while the
database was open (but even this didn't result in a wrong checksum; in
theory it could).

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