Jira MySQL collation health check fails with "The database collation 'utf8mb4_bin' and table collation 'utf8mb4_bin' are not supported by Jira."
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After migrating the collation in Jira's database to utf8mb4 following How to Fix the Collation and Character Set of a MySQL Database manually, the Health check fails with one of the following error messages "The database collation 'utf8mb4_bin' and table collation 'utf8mb4_bin' are not supported by Jira." or "The database collation 'utf8mb4_0900_ai_ci' and table collation 'utf8mb4_0900_ai_ci' are not supported by Jira." even though those collations are supported.
We recommend that you use the utf8mb4_bin collation, however utf8mb4_0900_ai_ci, which is the default collation for MySQL 8.0, is also supported.
Cause
In the dbconfig.xml, the database type is set to mysql instead of mysql57 (if using MySQL 5.7) or mysql8 (if using MySQL 8.0).
<database-type>mysql</database-type>Solution
In dbconfig.xml, set the database type to:
mysql57when using MySQL 5.7 (as described in Connecting Jira applications to MySQL 5.7)
<database-type>mysql57</database-type>OR
mysql8when using MySQL 8.0 (as described in Connecting Jira applications to MySQL 8.0)
<database-type>mysql8</database-type>Restart Jira for the configuration to be applied.