Instance Health Checks
Asked by Sabel Systems:

I keep getting this error in the Jira console. Running ver 8.4.1 and using SQL server 2014

The database collation 'SQL_Latin1_General_CP1_CI_AS' and table collation 'SQL_Latin1_General_CP1_CI_AS' are not supported by Jira

I have read several posts about the same message.

What is the fix?


Answers:
author: Alexis Robert
body: Hi [@Sabel Systems](/t5/user/viewprofilepage/user-id/3617868) ,

this means that your database collation is not configured properly, you are using a Case Insensitive collation whereas Confluence only supports Case Sensitive as you can see here : <https://confluence.atlassian.com/doc/database-setup-for-sql-server-9258.html#DatabaseSetupforSQLServer-2.Createadatabaseanddatabaseuser>

You will need to ask your database admin to fix the database collation.

Let me know if this works,

--Alexis

comments: author: Sabel Systems
body: Are there steps that someone could share to do this? I set the database up for this instance.


author: Sabel Systems
body: If I run this command, it breaks JIRA when it tries to start:

    ALTER DATABASE <database-name> COLLATE SQL_Latin1_General_CP1_CS_AS



author: Alexis Robert
body: Hi [@Sabel Systems](/t5/user/viewprofilepage/user-id/3617868) ,

the clean way to do this is to do a full XML export in Confluence first, and then setup Confluence with a new database (with the correct collation) and import the data.


author: Sabel Systems
body: Okay. What are the impacts to JIRA if I just leave as is?


author: Alexis Robert
body: The impact is that if you have 2 pages with the same title but different case, it will break stuff on your instance.

I would strongly recommend making sure the collation is correct before you go any further.


author: Sabel Systems
body: Okay. I created a brand new new database, ran the query specified:

    ALTER DATABASE MyDatabseName COLLATE SQL_Latin1_General_CP1_CS_AS

    Migrated my JIRA 8.4.1 instance from the internal database to new new database successfully

    And I get the same exact result.

    The database collation 'SQL_Latin1_General_CP1_CI_AS' and table collation 'SQL_Latin1_General_CP1_CI_AS' are not supported by Jira.

    Why do I keep getting this error?







author: Alexis Robert
body: If you just reimported the data on SQL Server, the database will keep its collation. Did you try to backup the data from Jira with the XML backup, then setup a new Confluence that points to the empty database, and import it using the Confluence wizard ?


author: Sabel Systems
body: Thank you for the quick reply.

Yes. Here is the process I used.

<https://confluence.atlassian.com/adminjiraserver072/switching-databases-828787577.html#Switchingdatabases-differenttype>

BTW, this is JIRA and NOT Confluence


author: Alexis Robert
body: Sorry, your post is tagged as "Confluence", did not realize it was for Jira. In this case, the correct collation is Latin1_General_CI_AI. You should setup a new empty database with this collation, then run the data import.


author: Sabel Systems
body: Sorry. I didnt realize that. So this is the correct query?

ALTER DATABASE jira_db COLLATE Latin1_General_CI_AI


author: Alexis Robert
body: Yes it should be this query. I think for SQL Server you can also do this directly in the interface too.


Tags: confluence-server

server