The instance health check reports: "The database collation 'SQL_Latin1_General_CP1_CI_AS' and table collation 'SQL_Latin1_General_CP1_CI_AS' are not supported by JIRA".
This appears after I had installed JiRA on our own server and used it for the first time. It would have been nice to know this requirement before I connected JiRA to my database. Because this is an error and not a warning, it must be fixed.
In my opinion I have 2 options. Either change the database collation, or start all over with the installation and connect to a proper database.
The first option brings me to hell if I beleive all the stories on many boards about changing collations in a database, so I prefer the second option. But that would result in a new license key request.
I'm not sure what to do.
Do you have any suggestions?
I assume you are using MS SQL? In our Database Setup for SQL Server documentation it does let you know that the collation needs to be SQL_Latin1_General_CP1_CS_AS (case sensitive). Did you have a chance to review this for the exact steps to create a database in MS SQL? If not, I would recommend reviewing it as there may be other settings that have been missed.
In terms of correcting it, you can follow this article:
I'm not sure what stories you're referring to exactly, but you will need to recreate the database with the proper settings, and migrate your data over to it.
You mentioned you needed a new license key request, but this migration won't require that you generate a new license key.
Let me know if you have any questions.
I have applied the procedure as described in your reference "How to fix the collation of an MS SQL database'.
In the end I try to open JiRA but get nothing in my browser.
In one of the log files (log\atlassian-jira.log), I see lots of error messages saying the entity definition does not match the database definition.
Column "SCHED_NAME" of table "dbo.JQUARTZ_BLOB_TRIGGERS" of entity "JQRTZBlobTriggers" is of type "NVARCHAR(120)" in the database, but is defined as type "VARCHAR(120)" in the entity definition.
But that's exactly what needed to be done in the describing document.
Now I'm confused.
JiRA does not start up any more.
It appears that your columns are defined with VARCHAR instead of NVARCHAR.
To move forward, I recommend the following procedure to migrate your database to a database where Jira has created the tables to avoid any issues.
We will be working off of the Switching databases documentation, scenario #2. Please make sure to follow exactly:
dbconfig.xmlfile in your JIRA home directory.
Please also take care to verify if you're using a supported version of SQL when migrating. If you are unsure, you can let me know your Jira and SQL version, and I can confirm for you.
I got it running again, using collation 'SQL_Latin1_General_CP437_CI_AI' and the option 'Is Read Committed Snapshot On'
That went well.
Did you know I had to enter the license key again (although there was a different ServerID) ?
Anyway, thanks for your help!
Thank you for letting me know. I'm happy you were able to get it working again. As your collation is not recommended, if you run into issues again you will need to attempt the migration as recommended earlier.
During a new setup you would have to enter the same license again, but there should be no need to generate a whole new one. If it asks you to do that again please let us know and we can help you get around that.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs