I used the recover tool. What should I look for in the SQL file generated by the recover?
On 18 fév, 08:27, Thomas Mueller <thomas.tom.muel...@gmail.com> 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 h2-database@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
