Import problem with JIRA DVCS Connector Plugin

Question

hi,

i'm trying to transfer from hsqldb to mysql, exported existing data, created mysql database, deleted dbconfig.xml and ran through the init. the import process gets to 90% then gives the following error:

2013-08-22 13:57:31,848 JiraImportTaskExecutionThread-1 INFO Mark James 837x245x1 1aqu90 10.1.11.112 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] Importing data is 90% complete...
2013-08-22 13:57:32,079 JiraImportTaskExecutionThread-1 INFO Mark James 837x245x1 1aqu90 10.1.11.112 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] Finished storing Generic Values.
2013-08-22 13:57:37,970 JiraImportTaskExecutionThread-1 ERROR Mark James 837x245x1 1aqu90 10.1.11.112 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] Error during ActiveObjects restore
com.atlassian.activeobjects.spi.ActiveObjectsImportExportException: There was an error during import/export with plugin JIRA DVCS Connector Plugin(com.atlassian.jira.plugins.jira-bitbucket-connector-plugin) #1.4.0.1 (table AO_E8B6CC_CHANGESET_MAPPING):
	at com.atlassian.activeobjects.backup.ImportExportErrorServiceImpl.newImportExportSqlException(ImportExportErrorServiceImpl.java:30)
	at com.atlassian.dbexporter.importer.DataImporter$BatchInserter.flush(DataImporter.java:512)
	at com.atlassian.dbexporter.importer.DataImporter$BatchInserter.executePS(DataImporter.java:488)
        at com.atlassian.dbexporter.importer.DataImporter$BaseInserter.execute(DataImporter.java:446)
	at com.atlassian.dbexporter.importer.DataImporter.importTable(DataImporter.java:125)
	at com.atlassian.dbexporter.importer.DataImporter.access$000(DataImporter.java:33)
	at com.atlassian.dbexporter.importer.DataImporter$1.call(DataImporter.java:73)
	at com.atlassian.dbexporter.importer.DataImporter$1.call(DataImporter.java:62)
	at com.atlassian.dbexporter.jdbc.JdbcUtils.withConnection(JdbcUtils.java:31)
	at com.atlassian.dbexporter.importer.DataImporter.doImportNode(DataImporter.java:61)
	at com.atlassian.dbexporter.importer.AbstractImporter.importNode(AbstractImporter.java:49)
	at com.atlassian.dbexporter.DbImporter.importData(DbImporter.java:73)
	at com.atlassian.activeobjects.backup.ActiveObjectsBackup.restore(ActiveObjectsBackup.java:158)
	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.restoreActiveObjects(DefaultDataImportService.java:467)
	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.performImport(DefaultDataImportService.java:673)
	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.doImport(DefaultDataImportService.java:273)
	at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:66)
	at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:29)
	at com.atlassian.jira.task.ImportTaskManagerImpl$TaskCallableDecorator.call(ImportTaskManagerImpl.java:146)

any suggestions gratefully received,

mark

Mark James3 · Answer

Doh! turns out mysql's (from apt-get on ubuntu) default character set was latin not utf8?? and certain foreign chars from github messages were causing it to fail. fix was to recreate db from mysql:

drop database jira;

create database jira default character set utf8 default collate utf8_unicode_ci;

Mark James3 · Answer

ps. another snippet from the log

Caused by: java.sql.SQLException: Incorrect string value: '\xC4\x9Flaya...' for column 'MESSAGE' at row 1