Upgrade from 6 to 7 - database collation problem and unable to dete issues

[Ozren Tomic]

Hello,

Recently we have upgraded our JIRA to v 7.7.

We're experiencing problem when we want to change project of issue, or when trying to delete it.
Only remaining warning that we have is "The table collation: 'Croatian_CI_AS' is unsupported by JIRA. The Database collation: 'Latin1_General_CI_AI' is supported by JIRA."

Error when trying to delete issue is:

"Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: An error occurred while converting the nvarchar value to JDBC data type INTEGER"

"Caused by: java.lang.NumberFormatException: For input string: "0|zzzzzz:""

Can you please advise what to do?

Thanks in advance,

Goran Kos

[Shannon S]

Hi Ozren,

Are you able to correct your collation using this article?

• How to fix the collation of a Microsoft SQL Server JIRA database

Let us know if you have any trouble.

Regards,

Shannon

[Ozren Tomic]

Hello,

Yes, we have already tried it but we're getting "The column "..." cannot be processed because more than one code page (1250 and 1252) are specified for it" during "Import data from the old database" step.

We don't have collation error in our log file (atlassian-jira.log) ... do you think that delete problem that we have is related to this collation issue?

We didn't see any problems working with issues. Create, update, close ... are working ok (except delete and change project)

Do you have any other solution for us?

Thanks in advance

[Shannon S]

Hi Orzren,

The error you are seeing is due to a collision restriction.

Please spin up a new MS SQL database according to our instructions, and then re-import your data to the new database with the correct collation. Once done you can connect JIRA to the new database and have the collation types resolved.

Let me know if you have any trouble.

Regards,

Shannon

[Ozren Tomic]

Hello Shannon,

Can you give me more info on "... then re-import your data to the new database with the correct collation"?

Thanks

[Shannon S]

Hi Ozren,

Your SQL admin should be able to assist with this, as there should be a native tool within SQL Server to do this. 

Have a look at Switching databases for further details.

Regards,

Shannon