For information
My connection string is:
jdbc:h2:file:D:\ProductDev\cockpitconsole\build\projects\mserver\dist
\h2\cockpit
\cockpit;MVCC=TRUE;AUTOCOMMIT=OFF;LOCK_MODE=3;LOG=2;CACHE_TYPE=SOFT_LRU
I change also some settings like:
statement.execute("set WRITE_DELAY 0");
statement.execute("SET MAX_MEMORY_ROWS 10000");
statement.execute("SET MAX_LOG_SIZE 32");Also, When I shutdow defrag the DB size moves from 12GB to 800 MB but after a Recover tool to extract SQL and a redo in a fresh DB the size is 200MB. After, I shutdown compact again and the DB size is 80 MB. I don't really understand how I can progress on the subject. It's very important for me because the DB grows on customer side (200MB per day for nothing) and I don't know how to fix it. On 18 fév, 08:27, Thomas Mueller <[email protected]> wrote: > Hi, > > > Can I add some debug settings on customer side? > > There are two options: > > - Use the trace options to analyze the JDBC method calls (append > ;TRACE_LEVEL_FILE=3 to the database URL) > > - Use the Recover tool to find out if there are uncommitted > transactions in the (large) database file (or a copy of the file; in > this case you could even copy the database file while it's in use, > because you don't need a 'save' copy of the database just to analyze > the transaction log). > > > Perhaps we need to implement some kind of default timeout on how long a > > transaction can stay open? > > Thats a very good idea. I wonder if other databases support something > like this? > > At the very least there should be a warning in the .trace.db file. I > will have a look at that. > > 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.
