Confluence Docs 3.3 : Migrating from HSQLDB to MySQL
This page last changed on Mar 04, 2010 by alaskowski.
DisclaimerMySQL Migration Toolkit is released by the makers of MySQL and as such, problems with the software should be directed to them. Atlassian Support does not offer support for the Migration Toolkit, nor do we provide support for this migration path. These instructions are offered for strictly informational purposes, and your mileage may vary.
Resources needed:
Preparation for migrating to MySQL from HSQLDB
Running the Migration ToolkitYou should be presented with the following screen. Choose Direct MigrationSource Database
Destination Database
Connecting to ServersYou should see the toolkit trying to connect. If you have problems, please click on the advanced options and sql will show you debugging information. Click Advanced to see the log. If you see "Java Heap Space: Out of Memory", you can start the MySQL Migration Toolkit with a -Xmx flag to allocate more memory to the JVM. After this screen you should come to reverse engineering. Click next. Source Schemata SelectionYou should see 2 databases, INFORMATION_SCHEMA and PUBLIC. Choose PUBLIC Object Type SelectionClick Next. Object Type MappingClick Show Details on both sections. For Migration Method for Type Schema, choose Multilanguage. For Migration Method for Type Table, choose Data Consistancy/Multilanguage Click Advanced. Check Enabled Detailed Mappings in Next Step Detailed Object MappingClick to rename the destination database to be the one set aside to migrate to. From this point on, you should be able to click next all the way through to finish the migration. ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Document generated by Confluence on Jul 09, 2010 01:08 |