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

Upgrade to 6.0.5 Fails due to Missing moved_issue_key Entry

XMLWordPrintable

      Steps to Reproduce

      Upgrade an existing instance of JIRA to 6.0.5

      Expected Results

      JIRA gets upgraded to 6.0.5

      Actual Results

      Upgrade process fails during the auto export and complains about a missing entry in the 'moved_issue_key' table.

      2013-07-24 13:11:25 error   
      Error occurred during export before upgrade: Error exporting data: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, OLD_ISSUE_KEY, ISSUE_ID FROM moved_issue_key (Table 'jiradb.moved_issue_key' doesn't exist)
      If necessary, auto-export can be disabled; see http://www.atlassian.com/software/jira/docs/latest/upgrade/autoexport.html
      com.atlassian.core.AtlassianCoreException: Error exporting data: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, OLD_ISSUE_KEY, ISSUE_ID FROM moved_issue_key (Table 'jiradb.moved_issue_key' doesn't exist)
      at com.atlassian.jira.bean.export.AutoExportImpl.exportData(AutoExportImpl.java:109)
      at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:376)
      at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:333)
      at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:100)
      at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:49)
      at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:117)
      at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:315)
      at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:209)
      at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:105)
      at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:30)
      at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:69)
      at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:33)
      at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:64)
      at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:54)
      at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791)
      at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
      at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
      at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
      at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
      at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      

      Workaround:

      Disable auto-export and attempt the upgrade again, or upgrade to 6.0.6

              malmeida Marcus Silveira
              cshim ChrisA
              Votes:
              10 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: