This is a fairly common problem to find after an upgrade to Jira. Some older versions of Jira were not checking for this. In some cases you might never notice a problem when running similar collations. However, since Atlassian is not testing every possible collation, it is probably best to correct this by creating a new database with the correct collation (as listed in the documentation) and then importing your existing data into that instance.
Steps on how I would recommend doing that are as follows:
By following these steps you can then import your previous data into a supported database with the correct database setup.
I would recommend avoiding trying to change the collation on an existing database, in theory it is possible, but I have found it can be difficult to do correctly, and this method is usually more successful.
The roof is on FIRE… network outages, broken processes, upset clients and employees. Each day seemed to bring more and more issues. Incidents were communicated via email, messengers (skype or teams) ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events