Hi, I could reproduce it. The problem is that the primary key index name of the table SYSTEM_LOB_STREAM (used for LOB content) conflicts with a primary key index name of your database.
With newer databases this is not a problem, because the primary key index names are not exported. With your database it is a problem. In the next version of H2, I will fix the SCRIPT command so the table SYSTEM_LOB_STREAM uses another index name that can't conflict (SYSTEM_LOB_STREAM_PRIMARY_KEY). If you can't wait for the next version, you could work around the problem. With the RunScript tool you could use the (currently undocumented) option "-continueOnError". I will document it. For details how to use the RunScript tool, see http://www.h2database.com/javadoc/org/h2/tools/RunScript.html#main_String... - after that you would need to create the missing primary key manually. 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 [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.
