We tested a change last night which broke up the select * on the lob table to select in batches of 1000 entries and it seems to have fixed the "Missing LOB" error. There were no "DB closed" errors either. Because the problem seems intermittent that's no guarantee that the issue has been fixed but it looks good so far.
It looks like we will have to turn MVCC back on because we are now hitting a large number of table lock timeouts but thats going to reintroduce the DB file growth issue. I know this feature is experimental but I guess my question is how experimental is it? and assuming the growth is down to long lived connections - is there any way to find out what selects / updates are still pending commits from the DB logs? On Thu, Jun 14, 2012 at 6:24 PM, Eoin Byrne <eoin...@gmail.com> wrote: > heh - tell me about it, having to wait 8 hours to see if a fix works can > make things difficult :) > > > On Thu, Jun 14, 2012 at 6:23 PM, Thomas Mueller < > thomas.tom.muel...@gmail.com> wrote: > >> Hi, >> >> Is there any other info you need? >>> >> >> Hm, a simple, reproducible test case would be great... ;-) >> >> 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. >> > > -- 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.
