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

JIRA upgrade process is not fully compatible with case sensitive collation

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Users who integrate JIRA with a MS SQL database with the case sensitive collation won't be able to perform upgrade of the application.

      There are a few upgrades task that are failing due to the case sensitive collation.

      2010-06-07 12:54:50,487 http-8081-1 ERROR anonymous 774x61x1 9l6cw1 127.0.1.1 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET  RESOLUTIONDATE = ?  WHERE  id = ?  (Invalid column name 'id'.)
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET  RESOLUTIONDATE = ?  WHERE  id = ?  (Invalid column name 'id'.)
	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:565)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.calculateResolutionDateForAllIssues(UpgradeTask_Build401.java:214)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.doUpgrade(UpgradeTask_Build401.java:116)

      or

      Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage 
SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: 
SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.)
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:552) 
at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build437.doUpgrade(UpgradeTask_Build437.java:63) 
at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:508)

      Users experiencing similar problems are recommended to create a new database with a case insensitive collation such as SQL_Latin1_General_CP437_CI_AI

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-21503 JIRA is not fully compatible with case insensitive collation

          • Medium - Medium priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22257 JIRA upgrade fail due to inconsistent SQL query case

          • Low - Low priority issues
          • Closed

          Suggestion - JRACLOUD-21506 JIRA upgrade process is not fully compatible with case sensitive collation

          • Closed

          Activity

            People

              Unassigned Unassigned
              bdziedzic Bogdan Dziedzic [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: