Hi,
This sounds like a corruption. I have a few questions:
- What is your database URL?
- Did you use LOG=0 or LOG=1? Did you read the FAQ about it?
- Did the system ever run out of disk space?
- Could you send the full stack trace of the exception including message
text?
- Did you use SHUTDOWN DEFRAG or the database setting DEFRAG_ALWAYS with H2
version 1.3.159 or older?
- How many connections does your application use concurrently?
- Do you use temporary tables?
- With which version of H2 was this database created?
You can find it out using:
select * from information_schema.settings where name='CREATE_BUILD'
or have a look in the SQL script created by the recover tool.
- Did the application run out of memory (once, or multiple times)?
- Do you use any settings or special features (for example cache settings,
two phase commit, linked tables)?
- Do you use any H2-specific system properties?
- Is the application multi-threaded?
- What operating system, file system, and virtual machine
(java -version) do you use?
- How did you start the Java process (java -Xmx... and so on)?
- Is it (or was it at some point) a networked file system?
- How big is the database (file sizes)?
- How much heap memory does the Java process have?
- 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?
- Could you send the .h2.db file where this exception occurs?
Regards,
Thomas
On Friday, April 13, 2012, Carl Hasselskog wrote:
> I recreated the database and now I got this error (after using it for a
> while).
>
> ERROR - FileDataBlockDB:jdbc[2] exception org.h2.jdbc.JdbcSQLException:
> General error: "java.lang.RuntimeException: page[14103] data node table:95
> entries:7 [20170, 20169, 20501, 20872, 21216, 25457, 27049, 27414] parent 0
> expected 15"; SQL statement:
> INSERT INTO FileDataBlocks ( filePath , dataBlockID, nodeID,
> relativeFileBackupTime, absoluteFileBackupTime, fileModificationTime,
> isDirectory, dataBlockSize , dataBlockVersionTimestamp ,
> fileStartPosition , dataBlockStartPosition , fileDataLength,
> FileChecksum, fileIsDeleted, fileVersionIsObsolete,
> rowModificationTime, dataBlockEncryptionKey,
> dataBlockCompressionAlgorithm, fileCompressionAlgorithm, fileData )
> VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?) [50000-166]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
> at org.h2.message.DbException.get(DbException.java:158)
> at org.h2.message.DbException.convert(DbException.java:281)
> at org.h2.table.RegularTable.addRow(RegularTable.java:139)
> at org.h2.command.dml.Insert.insertRows(Insert.java:124)
> at org.h2.command.dml.Insert.update(Insert.java:84)
> at org.h2.command.CommandContainer.update(CommandContainer.java:73)
> at org.h2.command.Command.executeUpdate(Command.java:226)
> at
> org.h2.jdbc.JdbcPreparedStatement.execute(JdbcPreparedStatement.java:181)
> at
> com.degoo.backend.databases.FileDataBlockDB.insertFileDataBlock(FileDataBlockDB.java:357)
> at
> com.degoo.backend.databases.FileDataBlockDB.addDataBlockToFileVersion(FileDataBlockDB.java:325)
> at
> com.degoo.backend.databases.FileDataBlockDB.addSmallFileOrDir(FileDataBlockDB.java:287)
> at
> com.degoo.backend.processor.streams.DataBlockInputStream.openNextFile(DataBlockInputStream.java:284)
> at
> com.degoo.backend.processor.streams.DataBlockInputStream.read(DataBlockInputStream.java:108)
> at java.io.InputStream.read(InputStream.java:171)
> at SevenZip.Compression.LZ.InWindow.ReadBlock(InWindow.java:48)
> at SevenZip.Compression.LZ.InWindow.MovePos(InWindow.java:101)
> at SevenZip.Compression.LZ.BinTree.MovePos(BinTree.java:67)
> at SevenZip.Compression.LZ.BinTree.GetMatches(BinTree.java:248)
> at SevenZip.Compression.LZMA.Encoder.ReadMatchDistances(Encoder.java:433)
> at SevenZip.Compression.LZMA.Encoder.GetOptimum(Encoder.java:701)
> at SevenZip.Compression.LZMA.Encoder.CodeOneBlock(Encoder.java:1108)
> at SevenZip.Compression.LZMA.Encoder.Code(Encoder.java:1283)
> at
> com.degoo.backend.processor.FileEncoder.createDataBlock(FileEncoder.java:169)
> at
> com.degoo.backend.processor.FileEncoder.createDataBlock(FileEncoder.java:134)
> at com.degoo.backend.processor.FileEncoder.iterate(FileEncoder.java:82)
> at
> com.degoo.backend.processor.scheduling.IdleRunnable.run(IdleRunnable.java:59)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.RuntimeException: page[14103] data node table:95
> entries:7 [20170, 20169, 20501, 20872, 21216, 25457, 27049, 27414] parent 0
> expected 15
> at org.h2.message.DbException.throwInternalError(DbException.java:228)
> at org.h2.index.PageDataIndex.getPage(PageDataIndex.java:239)
> at org.h2.index.PageDataNode.addRowTry(PageDataNode.java:128)
> at org.h2.index.PageDataIndex.addTry(PageDataIndex.java:167)
> at org.h2.index.PageDataIndex.add(PageDataIndex.java:130)
> at org.h2.table.RegularTable.addRow(RegularTable.java:121)
> ... 31 common frames omitted
>
>
> On Friday, April 13, 2012 12:12:08 PM UTC+2, Carl Hasselskog wrote:
>>
>> I don't have a reproducible test-case yet but I have some more info,
>> which I think might be related. When I'm trying to connect to the same
>> database I now get the following error:
>> ERROR - FileDataBlockDB:database close org.h2.message.DbException: File
>> corrupted while reading record: "index not found 34". Possible solution:
>> use the recovery tool [90030-166]
>> at org.h2.message.DbException.**get(DbException.java:169)
>> at org.h2.message.DbException.**get(DbException.java:146)
>> at org.h2.store.PageStore.**getPage(PageStore.java:804)
>> at org.h2.store.PageStore.**compact(PageStore.java:696)
>> at org.h2.store.PageStore.**compact(PageStore.java:524)
>> at org.h2.engine.Database.**closeOpenFilesAndUnlock(**Database.java:1198)
>> at org.h2.engine.Database.close(**Database.java:1148)
>> at org.h2.engine.Database.**removeSession(Database.java:**1027)
>> at org.h2.engine.Session.close(**Session.java:563)
>> at org.h2.jdbc.JdbcConnection.**close(JdbcConnection.java:363)
>>
>> The database has only one table so it is not unlikely that the problems
>> are related.
>>
>> On Friday, April 13, 2012 12:00:16 PM UTC+2, Carl Hasselskog wrote:
>>>
>>> I don't the undo-support is causing the problem but doesn't it
>>> seem unnecessary to track undos for ResultSets? I will try to create a
>>> simple reproducible case.
>>>
>>> Regards
>>> Carl
>>>
>>> On Thursday, April 12, 2012 9:13:22 PM UTC+2, Thomas Mueller wrote:
>>>>
>>>> Hi,
>>>>
>>>> Do you have a reproducible test case? If possible, could you send it?
>>>>
>>>>>
>>>>> 1. What does this do? log.addUndo(pageId, null);
>>>>> (in PageStore.java:1212)
>>>>>
>>>>> As in the comment in the source code, "ensure the undo entry is
>>>> already written".
>>>>
>>>>>
>>>>> 1. To me it looks like setting the page-parameter to null is what
>>>>> is causing the exception.
>>>>>
>>>>> No, it's just a verification.
>>>>
>>>>>
>>>>> 1. Wouldn't it be better to just delete the ResultSet-table
>>>>> without undo-support? Is there any use-case when you want to undo the
>>>>> closing of a ResultSet?
>>>>>
>>>>> I don't think that's the problem.
>>>>
>>>> Regards,
>>>> Thomas
>>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/h2-database/-/ZdPWECLasewJ.
> To post to this group, send email to
> [email protected]<javascript:_e({}, 'cvml',
> '[email protected]');>
> .
> To unsubscribe from this group, send email to
> [email protected] <javascript:_e({}, 'cvml',
> 'h2-database%[email protected]');>.
> For more options, visit this group at
> http://groups.google.com/group/h2-database?hl=en.
>
--
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.
