Hi, I think in this case the problem can be avoided by appending ;RECOVER=1 to the database URL. It looks like the log file is corrupt, or this is the wrong log file for the database.
Regards, Thomas On Mon, Sep 28, 2009 at 11:58 AM, Mike Goodwin <[email protected]> wrote: > Hi, > > So far this is a one off event that occurred recently. A database was > created inside our application in embedded mode with a minimal set of > data and default database settings using version 1.1.15. > (I should disclose it has a patch for hacking in some full outer join > support - the one i emailed to the list a while ago - but at this > point that code will not have been executed and i cannot see how it > could be a contributing factor). > > I have tried opening the database with our 1.1.15 and a vanilla 1.1.19 > in console mode and it has the same error each time. > > The database was not big (200kb), I tried deleting the index (no difference). > > Recovering this particular database is not important, but preventing a > recurrence is. I have kept hold of the broken database files in case > they are helpful. > > Please advise! > > Mike > > (stacktrace attached). > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
