Noel Grandin
Noel Grandin
You might also want to try doing a build from current HEAD and seeing it that fixes your issue, a few things have been fixed since the last release
What does your database URL look like?
Use the -XX:+HeapDumpOnOutOfMemoryError flag to the jvm to get a heap dump. Then fire up the VisualVM or the Eclipse MAT heap analyser and see where the memory is going...
You are querying your database by looping over every single row, and then decoding a JSON blob for every row. What did you expect? Of course it is going to...
Just to be clear - are you expecting the SCREENING table to the dropped? Because if so, that is not what CASCADE is designed to do. The intention is that...
So based on that stacktrace, the chunksToC cache is getting out of sync with the chunk.occupancy BitSet field. @andreitokar any ideas? I can't see what serialisation mechanism is keeping these...
The two files represent the Recover tools best guess as to the data structures. If you don't get useful data out of it, then I'm sorry, your DB is too...
It represents the internal data structures of the underlying storage engine. Only useful if you are familiar with the code.
Because the db file is corrupt.
Ah, apologies, my mistake. No, there is definitely something wrong with the Recover tool there. It should produce roughly the same output as running the SCRIPT command.