Running a recovery, the resulting db file is 5x larger, and still growing. I just had a bulk load deadlock. I'm not sure how to interrupt these things, but started with kill -INT, then kill -SEGV, then kill -KILL. After that the db could not be opened, and would dump a bunch of lines like this into the trace:
org.h2.jdbc.JdbcSQLException: Table "PROBEMAP_PROBES" not found; SQL statement: CREATE PRIMARY KEY PUBLIC.PRIMARY_KEY_E9 ON PUBLIC.PROBEMAP_PROBES(ID) [42102-175] 06-02 16:17:52 database: CREATE PRIMARY KEY PUBLIC.PRIMARY_KEY_E9 ON PUBLIC.PROBEMAP_PROBES(ID) I ran the recovery tool with java -cp ~/.m2/repository/com/h2database/h2/1.3.175/h2-1.3.175.jar org.h2.tools.Recover which generated a sql file that was 1.25x the size of the db file. I then loaded the script into a fresh db file with java -cp ~/.m2/repository/com/h2database/h2/1.3.175/h2-1.3.175.jar org.h2.tools.RunScript -url "jdbc:h2:recovered" -user '' -script cavm-testing.h2.sql which at the moment is more than 5x larger than the original db file. It's fairly remarkable. I may have to kill it. Any idea what would cause this, or if there's a way to prevent it? During the load which deadlocked the url was "cavm-testing;CACHE_SIZE=65536;UNDO_LOG=1;LOG=0;MVCC=TRUE" -- 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.
