[cosmo-dev] Cosmo db migration failure/corruption

[Randy Letness]

Scratch all of this.  All you have to do is re-run the migration with 
the updated migration jar.  No need to connect using ij and execute 
sql.  I just tried this.  You do have to make sure the updated derby.jar 
is in tomcat/common/lib before starting cosmo (remove the 10.2.2.0 and 
replace with 10.3.1.4).

-Randy

Randy Letness wrote:
> You can probably fix your db by doing the following:
>
> The database was upgraded to version 10.3.1.4 of derby during 
> migration, but the version in the server bundle is 10.2.2.0.  So the 
> first thing to do would be to
> grab the 10.3.1.4 derby jar and use ij to open the database and 
> execute the following sql stmts:
>
> alter table subscription drop column etag
> alter table users drop column etag
> alter table user_preferences drop column etag
> alter table item drop column etag
> alter table stamp drop column etag
> alter table attribute drop column etag
>
> Then, you should be able to re-run the migration using the updated 
> migration in 0.8.1 (not released yet).  You can wait until 0.8.1 is 
> released (likely Monday) or checkout the source from the 0.8 branch: 
> |http://svn.osafoundation.org/server/cosmo/branches/0.8 
> <http://svn.osafoundation.org/server/cosmo/trunk> and build the 
> migration component yourself.|
>