Antwort: Re: Migration to Scarab 0.21 and MySQL 5.1

Jorge,

I try to remember: Migration of our DB with about 10000 issues went 
flawlessly. There were some runtime problems I think depending on the 
generation of notifications (fk constraint violation). I'm sorry, that 
there are no more details, because of a re-deployment of the test Scarab 
app all the log files are lost.

If you try to reproduce the problem, you should import a scarab 0.21 DB 
into MySQL 4.1 or 5.1 with InnoDB configured and create new issue that is 
linked to some others as a possible duplicate. Notifications must be 
enabled, but there were no mails sent.

Regards,

Jörg Florin
Techniker Krankenkasse
Hauptverwaltung
IT-Systeme (ITS.4 - Systemframeworks)
Bramfelder Straße 140, D-22305 Hamburg
 
Tel: +49 (40) 69 09 - 25 75
Fax: +49 (40) 69 09 - 8 25 75
E-Mail: [email protected]
TK-Website: www.tk-online.de





"Jorge Uriarte Aretxaga" <[email protected]> 
 
Gesendet von: [email protected]
13.11.2008 16:49
Bitte antworten an
[email protected]


An
[email protected]
Kopie

Thema
Re: Migration to Scarab 0.21 and MySQL 5.1






I think there was some trick (disabling constraints while the migration 
takes place???) that might avoid that problem.
Anyway; could you elaborate which exactly was the problem you got? We 
might be able to fix the migration script so constraits don't get in the 
way...

Regards,

-- 
Jorge Uriarte Aretxaga
http://www.gailen.es
http://www.linkedin.com/in/jorgeuriarte 

On Thu, Nov 13, 2008 at 4:10 PM, <[email protected]> wrote:

Hello, 

as apposed to some mailings in this list and to the documentation I was 
able to successfully migrate a Scarab 0.20 DB to Scarab 0.21 with MySQL 
5.1. The only thing is, that you have to ensure to use MyISAM and not 
InnoDB because of some compatibility issues with constraints. This can be 
set in the initial configuration of MySQL or may be later changed in some 
place. MySQL 5 has some advantages, e.g. you can use a free graphical 
maintenance frontend (GUI Tools). 

My configuration: 

Scarab 0.21 
Windows Server 2003 
Apache Tomcat/6.0.18 
JVM: 1.6.0_10-b33
Database: mysql-5.1.29-rc-win32 (community) 

It is also possible to export the Database from MySQL 5.1 into a MySQL 4.x 
installtion, migrate it, and reimport it into MySQL 5.1. 

Viele Grüße
Jörg Florin
ITS.4 - Systemframeworks