Hi All

A customer of us was able to create a corrupt H2 database. Unfortunately I 
don't have much information on how he got there. I ran the H2 restore 
utilty on the corrupt DB and got tons of:

Error: java.io.IOException: Block not found in id [1, -120, 2, -103, -122, 
16] [1.4.187/50]
Error: java.io.IOException: Block not found in id [1, -78, 2, -102, -122, 
16] [1.4.187/50]
Error: java.io.IOException: Block not found in id [1, -123, 2, -101, -122, 
16] [1.4.187/50]


The database makes use of BLOBs and I noticed that in the recent version 
(1.4.188) there were fixes in this regard.

 - Is it possible to determine by analyzing the corrupt DB, the kind of 
corruption and if the recent fixes address the problem? 
 - If this cannot be done or too cumbersome, would you recommend to move 
away from MVSTORE back to PageStore? 
 - Is it possible that Windows is the origin of the problem (customer runs 
on Windows, us on Linux and OS X)?

The attached settings are from my machine (OS X).

Thanks a lot for any kind of help!



-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
CREATE_BUILD  187
info.BUILD_ID 187
info.VERSION_MAJOR  1
info.VERSION_MINOR  4
info.VERSION  1.4.187 (2015-04-10)
property.java.runtime.version 1.8.0_51-b16
property.java.vm.name Java HotSpot(TM) 64-Bit Server VM
property.java.vendor  Oracle Corporation
property.os.name  Mac OS X
property.os.arch  x86_64
property.os.version 10.10.4
property.sun.os.patch.level unknown
property.file.separator /
property.path.separator :
property.line.separator
property.user.country US
property.user.language  en
property.user.variant
property.file.encoding  UTF-8
EXCLUSIVE FALSE
MODE  REGULAR
MULTI_THREADED  0
MVCC  TRUE
QUERY_TIMEOUT 0
RETENTION_TIME  45000
LOG 2
ALIAS_COLUMN_NAME false
ANALYZE_AUTO  2000
ANALYZE_SAMPLE  10000
COMPRESS  false
DATABASE_TO_UPPER true
DB_CLOSE_ON_EXIT  true
DEFAULT_CONNECTION  false
DEFAULT_ESCAPE  \
DEFAULT_TABLE_ENGINE  null
DEFRAG_ALWAYS false
DROP_RESTRICT true
EARLY_FILTER  false
ESTIMATED_FUNCTION_TABLE_ROWS 1000
FUNCTIONS_IN_SCHEMA true
LARGE_TRANSACTIONS  true
LOB_TIMEOUT 300000
MAX_COMPACT_COUNT 2147483647
MAX_COMPACT_TIME  200
MAX_QUERY_TIMEOUT 0
MV_STORE  true
NESTED_JOINS  true
OPTIMIZE_DISTINCT true
OPTIMIZE_EVALUATABLE_SUBQUERIES true
OPTIMIZE_INSERT_FROM_SELECT true
OPTIMIZE_IN_LIST  true
OPTIMIZE_IN_SELECT  true
OPTIMIZE_IS_NULL  true
OPTIMIZE_OR true
OPTIMIZE_TWO_EQUALS true
OPTIMIZE_UPDATE true
PAGE_STORE_INTERNAL_COUNT false
PAGE_STORE_MAX_GROWTH 131072
PAGE_STORE_TRIM true
QUERY_CACHE_SIZE  8
RECOMPILE_ALWAYS  false
RECONNECT_CHECK_DELAY 200
REUSE_SPACE true
ROWID true
SELECT_FOR_UPDATE_MVCC  true
SHARE_LINKED_CONNECTIONS  true
info.FILE_WRITE 0
info.FILE_READ  85
info.PAGE_COUNT 237348
info.PAGE_SIZE  4096
info.CACHE_MAX_SIZE 16
info.CACHE_SIZE 0

Reply via email to