Hi, If the database is already corrupt, then I'm afraid you will need to re-create it (for example, via export to SQL script and re-import).
Bug fixed since version 1.3.168: With version 1.3.171 and older: when using local temporary tables and not dropping them manually before closing the session, and then killing the process could result in a database that couldn't be opened. Regards, Thomas On Fri, Jun 27, 2014 at 12:11 PM, Noel Grandin <[email protected]> wrote: > > For starters, I would suggest updating to 1.3.176. > You appear to be running 1.3.168, which is a couple of versions out of > date, and we've fixed a lot of issues since then. > > > > On 2014-06-27 10:15 AM, Noel Grandin wrote: > >> >> >> On 2014-06-26 02:14 PM, Sanjeev Gour wrote: >> >>> Here it is- >>> >> >> You chopped off the most important part of the exception. >> >> > -- > 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. > -- 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.
