Incorrect database collation setting can cause errors/failures in the Git Integration for Jira application.
Jira admins will see a message similar to the one below in the Jira log:
Health Check: Collation
Name: Collation Is healthy: false Failure reason: The database collation 'utf8_bin' and table collation 'utf8_bin' are not supported by Jira. Severity: CRITICAL
This check retrieves the collation of the database and determines if it is within the list of collations supported by Atlassian. The Check will not assess collation when using an embedded (H2/HSQL) database and will fail if it cannot successfully identify the database (MariaDB is being used, for example). It fails if the collation does not match what we expect, or it cannot be retrieved due to an exception checking it. This health check does not report any warnings for Postgres database users. If you experience an error on this health check, the steps in the resolution should be applied.
Atlassian – Health Check: Database Collation
Follow instructions from Atlassian:
Microsoft SQL Server: Health Check: Database Collation in Microsoft SQL Server
PostgreSQL: Health Check: Database Collation in PostgreSQL
Oracle: Health Check: Database Collation in Oracle
If you still have a question – reach out to our Support Desk or email us at firstname.lastname@example.org.
More articles about troubleshooting, workarounds and solutions
Why I am getting the error, “git-upload-pack not permitted”?
Avoid OutOfMemory exceptions by configuring or memory allocation with Jira to accommodate large repositories
Cannot auto-deploy some tracked repositories: Specified origin is incorrect or not supported
Connection Reset when Accessing the Database
"Dangerous use of multiple connections" error on local database
Duplicate entry 0 for key PRIMARY exceptions in log
Error while reindexing – Java heap space / Object too large, rejecting the pack
Gitolite integration: Why the Git integration app not see the master branch?
Health Check: Database Collation (this page)
Indexing error – Too many open files
Installation fails when installing manually
Jira index error: IndexNotFoundException: no segments* file found
Malformed input or input contains unmappable characters
Personal access token failing Azure DevOps integration with Not Authorized error
Problems with shared home on Azure Storage
Pull request index error: org.json.JSONException
Repositories missing from Azure DevOps integration
"Service proxy has been destroyed" exceptions in log
SQLException ‘Incorrect string value’ in merge requests
SSH key file format is invalid
TFS – Not authorized exception when Jira works thru proxy
Unexpected exception parsing XML document from URL error in log