Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-59077

Latin1_General_CI_AI shown as unsupported database in JIRA's Health Check

      Summary

      Latin1_General_CI_AI shown as unsupported database in JIRA's Health Check. According to KB here it is shown as supported.

      Environment

      7.0.0, 7.0.2, 7.0.4

      Steps to Reproduce

      1. Create Latin1_General_CI_AI database in Microsoft SQL Database.
      2. Connect JIRA to the database.
      3. In JIRA, health checker will show error saying The database collation 'Latin1_General_CI_AI' is not supported by JIRA.

      Expected Results

      Health checker should display Latin1_General_CI_AI as supported database*

      Actual Results

      Health checker display The database collation 'Latin1_General_CI_AI' is not supported by JIRA.

      Workaround

      Currently there is no workaround for this issue.

            [JRASERVER-59077] Latin1_General_CI_AI shown as unsupported database in JIRA's Health Check

            This message is still occuring after updating Jira to Version 7.6.2, although obviously no real issue rised

            Harald Fister added a comment - This message is still occuring after updating Jira to Version 7.6.2, although obviously no real issue rised

            I can confirm the same issue when upgrading from 7.3.6 to 7.6.0 - this was not an issue when moving from 7.0 to 7.3.6.

            Paul Barber added a comment - I can confirm the same issue when upgrading from 7.3.6 to 7.6.0 - this was not an issue when moving from 7.0 to 7.3.6.

            GBE added a comment -

            The problem still exists in 7.5.3

            When my instance first starts it states:

            GBE added a comment - The problem still exists in 7.5.3 When my instance first starts it states:

            Jason Caranzo added a comment - - edited

            installing the Health Plugin resolve the problem but all active sprints was removed.

            is this a bug?

            Jason Caranzo added a comment - - edited installing the Health Plugin resolve the problem but all active sprints was removed. is this a bug?

            Hi,

            This issue has been fixed in the latest release of the JIRA Instance Health Plugin.

            I have copied this issue for the problem relating to the collation in the logs. JRA-59378

            Matt Jones (Inactive) added a comment - Hi, This issue has been fixed in the latest release of the JIRA Instance Health Plugin . I have copied this issue for the problem relating to the collation in the logs. JRA-59378

            Hi jason.smith10171257379257,

            As per the message it is an unsupported collation, this is detailed in https://confluence.atlassian.com/display/JIRAKB/Health+Check%3A+Database+Collation

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi jason.smith10171257379257 , As per the message it is an unsupported collation, this is detailed in https://confluence.atlassian.com/display/JIRAKB/Health+Check%3A+Database+Collation Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            How about this one?

            The database collation 'latin1_swedish_ci' and table collation 'latin1_swedish_ci' are not supported by JIRA.

            Jason Smith added a comment - How about this one? The database collation 'latin1_swedish_ci' and table collation 'latin1_swedish_ci' are not supported by JIRA.

            The 2.1.1 release of the Instance Health Plugin seems to have resolved this issue. Thanks!

            Matson Money added a comment - The 2.1.1 release of the Instance Health Plugin seems to have resolved this issue. Thanks!

            Hi all,

            I have done an investigation on the topic, and for JIRA's current database model (7.0.x and above) it really doesn't matter whether the SQL_xxx or xxx collation (Windows) is used.

            Expanding on this, the difference only affects the storage on non-unicode text storage types (text, char, varchar) and JIRA's current schema does not specify columns of these types. Both SQL and Windows collations use the same rules for Unicode types.

            Consequently, we will expand the list considered by the startup check such that the Windows variant of the permitted collations are not flagged as unsupported.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - - edited Hi all, I have done an investigation on the topic, and for JIRA's current database model (7.0.x and above) it really doesn't matter whether the SQL_xxx or xxx collation (Windows) is used. Expanding on this, the difference only affects the storage on non-unicode text storage types (text, char, varchar) and JIRA's current schema does not specify columns of these types. Both SQL and Windows collations use the same rules for Unicode types. Consequently, we will expand the list considered by the startup check such that the Windows variant of the permitted collations are not flagged as unsupported. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            The message in atlassian-jira.log reads:

                ****************************************************************************************************
                You are using an unsupported mssql collation: Latin1_General_CI_AI. This may cause some functionality to not work.
                Please use SQL_Latin1_General_CI_AI or SQL_Latin1_General_CP437_CI_AI as the collation instead.
                ****************************************************************************************************
            

            So either the documentation needs to be updated to mention SQL_Latin1_General_CI_AI instead of Latin1_General_CI_AI or the check needs to be fixed.

            Glenn Verrijkt added a comment - The message in atlassian-jira.log reads: **************************************************************************************************** You are using an unsupported mssql collation: Latin1_General_CI_AI. This may cause some functionality to not work. Please use SQL_Latin1_General_CI_AI or SQL_Latin1_General_CP437_CI_AI as the collation instead. **************************************************************************************************** So either the documentation needs to be updated to mention SQL_Latin1_General_CI_AI instead of Latin1_General_CI_AI or the check needs to be fixed.

              majones Matt Jones (Inactive)
              vshanmugam Vicknesh Shanmugam (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: