We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-59378

Log messages indicate Latin1_General_CI_AI shown as unsupported database collation for MySQL while health check passes

      Summary

      Latin1_General_CI_AI shown as unsupported database in JIRA's logs:

      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.
          ****************************************************************************************************
      

      Steps to Reproduce

      1. Create Latin1_General_CI_AI database in Microsoft SQL Database.
      2. Connect JIRA to the database.
      3. Restarting JIRA shows the error in the logs.

      Expected Results

      The logs should not fail on this collation for Microsoft SQL Server.

      Actual Results

      The collation is reported as unsupported. Latin1_General_CI_AI is supported.

      Workaround

      Ignore the Error in the logs and confirm the supported collation with the JIRA Instance Health Add-on..

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-59378

            Log messages indicate Latin1_General_CI_AI shown as unsupported database collation for MySQL while health check passes

                Summary

                Latin1_General_CI_AI shown as unsupported database in JIRA's logs:

                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.
                    ****************************************************************************************************
                

                Steps to Reproduce

                1. Create Latin1_General_CI_AI database in Microsoft SQL Database.
                2. Connect JIRA to the database.
                3. Restarting JIRA shows the error in the logs.

                Expected Results

                The logs should not fail on this collation for Microsoft SQL Server.

                Actual Results

                The collation is reported as unsupported. Latin1_General_CI_AI is supported.

                Workaround

                Ignore the Error in the logs and confirm the supported collation with the JIRA Instance Health Add-on..

                        Unassigned Unassigned
                        vshanmugam Vicknesh Shanmugam (Inactive)
                        Votes:
                        30 Vote for this issue
                        Watchers:
                        52 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            vshanmugam Vicknesh Shanmugam (Inactive)
                            Affected customers:
                            30 This affects my team
                            Watchers:
                            52 Start watching this issue

                              Created:
                              Updated:
                              Resolved: