Error when Switching Database from h2 to MySQL 5.6

[Jason Galea]

Hi,

We are trying to perform a database switch on our JIRA Server from h2 to MySQL 5.6

We did configure the database correctly according to the database setup documentation.

Here are the steps we used for the JIRA migration:

- Perform a system backup (using the h2 Database)
- Fix the file just in case there are any errors using this method: https://confluence.atlassian.com/jira/removing-invalid-characters-from-xml-backups-12079.html\\ - Stopped the JIRA service
- renamed the dbconfig.xml
- Started the JIRA service
- Set up the new connection with the new database
- Performed the import
- BOOM.... error after 100% import progress

We are currently running JIRA 7.9.2 on a CentOS 7 using an h2 database and we would like to find a way how to start using an external database but this issue keeps happening.  

Any suggestions?

Cheers,
Jason

[Vickey Palzor Lepcha]

I hope you did not miss the jdbc driver - that is a very well known issue during DB connectivity.

[Andy Heinzer]

I'd like to look at the log file this error references.  You can find this in the $JIRAHOME/log/atlassian-jira.log file.   I would expect this log will have a more complete stacktrace that provides more clues on this problem.

On a side note, using MySQL with Jira is possible, but it has an additional step that using other supported databases do not have with jira: You have to manually download the JDBC Connector/J 5.1.x version from MySQL's site and extract the .jar file there into the $JIRAINSTALL/lib/ folder.   I suspect you did this already, or otherwise you would not have been able to get this far, but I have seen other users trying to use the version 8.x version of that driver and have other problems with Jira.

But either way, I'd be interested to see you log file from startup through to this error.  Perhaps you can post this file to a sharing site like dropbox or google drive so we can take a look at the details in the logs.