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

JIRA upgrade fail due to inconsistent SQL query case

    XMLWordPrintable

Details

    • 4.01
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 16 November 2017

      Hi everyone,

      The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low.
      Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out.

      Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

      Cheers,
      Ignat Alexeyenko
      Jira bugmaster.

      Show
      Atlassian Update – 16 November 2017 Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

    Description

      As some of the database has a case-sensitive identifiers (column header names), upgrading JIRA version is impossible. When performing XML export, JIRA use lower and uppercase SQL query randomly causing error to the case-sensitive database (eg. Sybase ASE):

      Error occurred during export before upgrade: Error in action: com.atlassian.jira.action.admin.DataExport@634ae081, result: error Error exporting data: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, USERNAME, PAGENAME, DESCRIPTION, SEQUENCE, FAV_COUNT, LAYOUT, ppversion FROM portalpage (Invalid column name 'ID'. )

      From the above error during the XML export, JIRA use SQL query with the uppercase column name 'ID'. Although the table is changed to have a uppercase column name 'ID', the below error is generated with invalid column name 'id':

      2010-09-13 10:22:58 error Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE 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 portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'. )

      JIRA should have a standardized SQL query so that case-sensitive database (eg. Sybase ASE) will be compatible with JIRA also

      Attachments

        Issue Links

          is related to

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

          • Closed

          Activity

            People

              Unassigned Unassigned
              klfoong Foong (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: