> > If the error code is really "[90017-136]", that would mean you are > actually using H2 version 1.2.136 from 2010-05-24. Could you verify > this? > Yes, that is correct, my bad. I got the error first using 1.3.157:
Attempt to define a second primary key; SQL statement: <https://192.168.0.130:8082/test.do?jsessionid=4068285b540ada30b1c2fd9a8ab657bb#>CREATE PRIMARY KEY IF NOT EXISTS INFORMATION_SCHEMA.PRIMARY_KEY_3 ON INFORMATION_SCHEMA.LOB_MAP(LOB, SEQ) [90017-157]<https://192.168.0.130:8082/test.do?jsessionid=4068285b540ada30b1c2fd9a8ab657bb#> 90017/90017 Then tried it with 1.2.136 which was also available on the machine. > I found and fixed the problem now (in the trunk). Unfortunately, you > will need to use the Recover tool to restore the data. I'm sorry about > that. I will release a new version at the end of the week. Until then, > I suggest to use version 1.3.155 if possible. > I dumped the SQL data using the recovery tool like this: $ java -cp h2-1.3.157.jar org.h2.tools.Recover -dir /path/to/database-dir -db database-name Then I removed the database files *.db and successfully connected using the older H2 version, created a new database and copy&pasted the SQL output from the recovery tool into the web console. Now the database is up and running correctly again. Thanks for your help! Cheers, tobi -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/b6HcV4LBYaAJ. 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.
