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:
- Select a database type/version from our Supported platforms - Atlassian Documentation
- Create a new blank database per Connecting JIRA to a database, (paying close attention to the correct collation for that database type)
- Gather an XML backup of your JIRA instance. Even if you can't start JIRA, you can still find a recent one of these backups in the filesystem of the JIRA server. By default this is saved in <jira-home>/export/ folder
- Stop JIRA,
- Run the JIRA Configuration tool to tell JIRA to use the new blank database, save these changes, (if you can't run this, then you can just directly edit the <jira-home>/dbconfig.xml file to make these changes)
- Start JIRA up again (when JIRA starts with an empty database, it automatically launches the setup wizard)
- Copy the export XML zip file from <jira-home>/export/ into <jira-home>/import/
- Then you can import the backup using the 'Import your data' link in the setup wizard
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.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.