jira restore problem when Migration server

wanwan

Hello,<br>when I Migration server and use XML bakupfiles to restore the jira,it shows:<br><br>1&#12289;JiraImportTaskExecutionThread-1 ERROR root 1025x34x1 15p19z3 192.168.2.167 /secure/admin/XmlRestore.jspa [c.a.upgrade.core.DefaultUpgradeTaskFactoryProcessor] Upgrade task [host,buildNumber=77001] failed<br>java.lang.RuntimeException: Error running original upgrade task<br><br>2&#12289;Caused by: com.querydsl.core.QueryException: Caught SQLException for delete from clusteredjob<br>where clusteredjob.id not in (select max(jobs.id)<br>from (select preload.id, preload.job_id<br>from clusteredjob preload) as jobs<br>group by jobs.job_id)<br>at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:50)<br>at com.querydsl.sql.dml.SQLDeleteClause.execute(SQLDeleteClause.java:222)<br>at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build77001.lambda$doUpgrade$0(UpgradeTask_Build77001.java:54)<br>at com.atlassian.jira.database.DefaultQueryDslAccessor$1.lambda$executeQuery$0(DefaultQueryDslAccessor.java:85)<br>at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(DatabaseAccessorImpl.java:68)<br>at com.atlassian.jira.database.DefaultQueryDslAccessor$1.executeQuery(DefaultQueryDslAccessor.java:84)<br>at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build77001.doUpgrade(UpgradeTask_Build77001.java:53)<br>at com.atlassian.jira.upgrade.AbstractUpgradeTask.runUpgrade(AbstractUpgradeTask.java:61)<br>... 34 more<br><br>3&#12289;Caused by: java.sql.SQLException: You can't specify target table 'clusteredjob' for update in FROM clause<br><br>my server is centos 7.3,mysql:5.7.8-0.3,mysql-connect:mysql-connector-java-5.1.47-bin.jar,jira:7.9-->7.9<br>the XML backup zip file has:
&#9500;&#9472;&#9472; activeobjects.<span>xml</span>
<span>&#9500;&#9472;&#9472; entities</span>.<span>xml</span>

 

Andy Heinzer

Hi,

Jira is failing to run this upgrade task due to a known bug in versions of MySQL between 5.7.0 and 5.7.17.  We track this from Jira's side in JRASERVER-67169

MySQL is tracking that bug in https://bugs.mysql.com/bug.php?id=79590

Technically this is not something Jira itself can fix.   Instead the solution here is to get to a database version that won't have this bug.

MySQL 5.7.18 and Later won't have this problem.  So I would recommend that you either update your database or migrate your Jira database to a version of Mysql 5.7.18 or higher OR to a different supported database type, such as postgresql.   This way you should then be able to complete this upgrade/migration of your data successfully.

I hope this helps.

Andy