[cosmo-dev] Cosmo db migration failure/corruption

[Mike Dawson]

I've been backing up the wrong db for the past 6 weeks.  I can read the 
derby database with ij.  Do you know what exactly would be broke?

Is there any migration procedure for moving from derby to mysql?  Would 
dumping all the tables to text and importing them into a clean mysql 
instance work in theory?

Mike

Randy Letness wrote:
> Yes, this is a bug.  I opened 
> https://bugzilla.osafoundation.org/show_bug.cgi?id=11148 Did you backup 
> your database before running migration?  If so, then you can continue to 
> use 0.7.x until this bug is fixed.  Otherwise the failed migration 
> probably put the db into an unusable state.
> 
> -Randy
> 
> Mike Dawson wrote:
>> The problem seems to be in 
>> cosmo-migration-0.8-jar-with-dependencies.jar/110-to-120-Derby-pre.sql:
>>
>> update attribute set etag='';
>> update stamp set etag='';
>>
>> Removing the semi-colons allows it to run without error.
>>
>> Cosmo still fails to start for me though - did my db get corrupted by 
>> running the failed migration on it?
> 
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev