Emmanuel, Thanks for emailing.
The original column type is the same as that restored by Octopus. My backends and controller are running on the same machine (different ports). All running database backends are using the exact schemas. Just a guess, but I tend to think that the Sequoia restore has problems with duplicate name syntax for columns (in different tables). I really hope for a resolution since I am very close to using Sequoia as our Cluster solution (assuming I can do a dynamic restore/enable). If necessary, I hope you can implement a HSQL backuper as I have already tried (quite unsuccessfully). :( Thanks for any help, -Jared -----Original Message----- From: Emmanuel Cecchet [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 24, 2006 4:31 PM To: Box, Jared C Cc: [email protected] Subject: Re: DB backend dynamically loaded disables on first write Hi Jared, > 2006-10-24 11:14:59,792 INFO backup.backupers.OctopusBackuper Starting > restore of backend localhost17 from checkpoint jdump > 2006-10-24 11:15:13,335 INFO controller.RequestManager.myDB Recovery of > backend localhost17 done. > 2006-10-24 11:17:23,996 ERROR controller.RequestManager.myDB Failed to > merge current schema because of Unable to merge table > [FRIENDLY_UNIT_MISSIONS]: column 'MISSIONS_ID' definition mismatch. > java.sql.SQLException: Unable to merge table [FRIENDLY_UNIT_MISSIONS]: > column 'MISSIONS_ID' definition mismatch > When you enable a backend in RAIDb-1, Sequoia checks that the database schemas of all backends are the same (we are supposed to replicate the same database after all). The issue here is that once Octopus has restored your database, it seems that the type of your column MISSION_ID in the table FRIENDLY_UNIT_MISSIONS is not the same as the one of the already enabled backend. Could you check what was the original type of the column and what is the type that Octopus restored? If this does not work, we will probably have to come out with another backuper for HSQL. I recently commited a new TarBackuper that could probably be re-used to simply implement an hsqldb backuper. Are your HSQLDB instances running on the same machine as the controller ? Thanks for your feedback, Emmanuel -- Emmanuel Cecchet Chief Architect, Continuent Blog: http://emanux.blogspot.com/ Open source: http://www.continuent.org Corporate: http://www.continuent.com Skype: emmanuel_cecchet Cell: +33 687 342 685 _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
