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

Unable to setup JIRA using the setup Wizard even after a database error occurs on import

    XMLWordPrintable

Details

    • 4.01
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 November 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 06 November 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

      1. Connect to an empty oracle database.
      2. On the JIRA setup wizard choose restore some data.
      3. I restored my local data. it had an issue with a summary > 255 characters and I got this error:
      java.sql.SQLException: ORA-12899: value too large for column "TREVOR"."JIRAISSUE"."SUMMARY" (actual: 414, maximum: 255)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
        at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
        at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
        at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)
        at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1008)
        at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
        at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
        at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3530)
        at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1062)
        at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:233)
        at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:632)
        at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:125)
        at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:98)
        at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:64)
        at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:489)
        at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:469)
        at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:80)
        at com.atlassian.jira.action.admin.OfbizImportHandler.createWithDeadlockRetry(OfbizImportHandler.java:515)
      1. I then go back to the initial wizard and click "Next" to setup JIRA rather than do an import.
      2. (DEFECT) The next button takes me to a screen that says JIRA has been setup. However, this leaves JIRA in a bad state as some of the data from the initial import is hanging around in the database. After this point JIRA is non-usable.

      I would assume that if I restart the "clean install" setup wizard, that it cleans up the database so it actually did a clean install.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bbain bain
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: