Boards are not restoring from backup to db Edited

Hi,
we have an issue with backup boards to database. After restoring xml files all tables are creating, complementing but tables with boards and sprints are empty.
We are migrating from PostgreSQL - 9.5.6 to MSSQL 2012 on Azure.
Let me describe the whole process which I used.
So our company decided to migrate to mssql. On our production server we have JIRA 7.3.0 but we want to use the newest version. So i copied our production server and i upgraded to newest version. Next I copied attachments, indexes and plugins to our new VM. Then I made restore. Then I started new VM.
First issue that i see after connecting to new db is issue due to collation error. You are recommending to use Latin1_General_CI_AI so we choose this collation but after fist jira initializiation there was an error with suggestion to use SQL_Latin1_General_CI_AI but on Azure we cant choose these collation, only Latin1_General_CI_AI.
After these i made backup from zip file but boards didnt restore. I was getting java.lang.IllegalArgumentException: Unsupported field encountered: binary but after restarting server the error dissapeared. Then i made indexing.
Summarazing the whole things. Tables for boards, i.e AO_60DB71_RAPIDVIEW are still empty.
I used your instructions on attlassian sites but there are not helpful for me.
Any ideas how to fix that issue?

 

3 answers

1 accepted

0 vote

Just to circle back on this case:

We found that this error was caused by a bug to a plugin, Xporter.  In turn there exists a bug report for this in https://jira.xpand-addons.com/browse/XPORTER-834

The problem here is that older versions of this plugin would create XML backups that could not be restored in Jira.  We were able to resolve this by going back to the source Jira instance and updating this plugin there to a version such as 5.1.1 or higher.  That way we could create an updated XML backup that can then be restored in the destination instance.

1 vote

You don't say how you backed up or restored the database - you just say "made backup".  Was this XML via the UI, or a database dump and restore or something else?

Via UI. But i say that i made it from zip so I thought that was clear. 

I'm afraid it was not that clear, no, but it is now, and it's the only thing that was not clear.

An xml export and import should have restored everything.  Missing boards suggests the restoration has not worked properly.

Do you have any errors in the logs from when you did the upgrade or the xml restoration?

It is possible that the XML import process failed, but Jira still appears to work anyways.  The logs from the time of the import though would indicate if there was a problem here.  I'm expecting there is probably some kind of SQL exception that happens during this XML restore with more details.

The XML import will have a percentage that should run from 1% to 100%.   If you're logs don't reach 100%, then the import was incomplete and we should look more closely at the error in the logs from that time in order to understand how to fix this.

I will check that. I forgot to add that issuses and projects imported corecctly.

Logs from beginning of restore
2017-11-29 09:04:17,440 http-nio-8080-exec-9 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.w.action.util.ImportAll] Running ImportAll
2017-11-29 09:04:17,446 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Running JIRA Data Import...
2017-11-29 09:04:17,475 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing XML data...
2017-11-29 09:04:17,697 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 1% complete...
2017-11-29 09:04:17,815 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 2% complete...
2017-11-29 09:04:17,934 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 3% complete...
2017-11-29 09:04:18,059 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 4% complete...
2017-11-29 09:04:18,171 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 5% complete...
2017-11-29 09:04:18,260 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 6% complete...
2017-11-29 09:04:18,389 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 7% complete...
2017-11-29 09:04:18,450 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 8% complete...
2017-11-29 09:04:18,505 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 9% complete...
2017-11-29 09:04:18,562 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 10% complete...
2017-11-29 09:04:18,612 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 11% complete...
2017-11-29 09:04:18,663 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 12% complete...
2017-11-29 09:04:18,745 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 13% complete...
2017-11-29 09:04:18,864 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 14% complete...
2017-11-29 09:04:18,971 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 15% complete...
2017-11-29 09:04:19,031 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 16% complete...
2017-11-29 09:04:19,102 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 17% complete...
2017-11-29 09:04:19,216 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 18% complete...
2017-11-29 09:04:19,272 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 19% complete...
2017-11-29 09:04:19,321 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 20% complete...
2017-11-29 09:04:19,508 JiraImportTaskExecutionThread-1 DEBUG Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] startCleaning
2017-11-29 09:04:20,474 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:25,894 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:30,974 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:36,066 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:41,147 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:46,207 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:51,269 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:56,277 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:04:59,293 JiraImportTaskExecutionThread-1 DEBUG Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] stopCleaning
2017-11-29 09:04:59,293 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Removing all entries from the database.
2017-11-29 09:05:01,284 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:06,307 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:11,315 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:16,332 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:21,367 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:26,426 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:31,506 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:36,516 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:41,523 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:46,536 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:51,545 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:05:56,552 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:06:01,560 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:06:06,569 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:06:11,576 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active

2017-11-29 09:07:16,723 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:21,730 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:26,736 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:31,758 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:34,359 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] All entries removed.
2017-11-29 09:07:34,359 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Started storing 163703 Generic Values.
2017-11-29 09:07:34,592 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 21% complete...
2017-11-29 09:07:34,694 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 22% complete...
2017-11-29 09:07:34,707 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 23% complete...
2017-11-29 09:07:36,879 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:38,926 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 24% complete...
2017-11-29 09:07:41,989 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:44,240 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 25% complete...
2017-11-29 09:07:47,084 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:48,443 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 26% complete...
2017-11-29 09:07:52,147 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:52,974 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 27% complete...
2017-11-29 09:07:57,270 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:07:57,599 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 28% complete...
2017-11-29 09:08:02,349 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:08:03,224 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 29% complete...
2017-11-29 09:08:07,457 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:08:07,693 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 30% complete...
2017-11-29 09:08:11,616 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 31% complete...
2017-11-29 09:08:12,552 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:08:15,865 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 32% complete...
2017-11-29 09:08:17,660 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...

And this warning is going the same 90%. Then i have this.
2017-11-29 09:13:04,351 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 90% complete...
2017-11-29 09:13:04,913 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:10,006 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:15,099 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:19,613 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Finished storing Generic Values.
2017-11-29 09:13:19,623 JiraImportTaskExecutionThread-1 DEBUG Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] startCleaning
2017-11-29 09:13:19,877 JiraImportTaskExecutionThread-1 DEBUG Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] stopCleaning
2017-11-29 09:13:20,106 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:25,162 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:30,416 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:33,992 JiraImportTaskExecutionThread-1 ERROR Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.IllegalArgumentException: Unsupported field encountered: binary
java.lang.IllegalArgumentException: Unsupported field encountered: binary
at com.atlassian.dbexporter.importer.DataImporter$BaseInserter.setValue(DataImporter.java:372)
at com.atlassian.dbexporter.importer.DataImporter.importTable(DataImporter.java:112)
at com.atlassian.dbexporter.importer.DataImporter.access$000(DataImporter.java:41)
at com.atlassian.dbexporter.importer.DataImporter$1.call(DataImporter.java:71)
at com.atlassian.dbexporter.importer.DataImporter$1.call(DataImporter.java:64)
at com.atlassian.dbexporter.jdbc.JdbcUtils.withConnection(JdbcUtils.java:28)
at com.atlassian.dbexporter.importer.DataImporter.doImportNode(DataImporter.java:64)
at com.atlassian.dbexporter.importer.AbstractImporter.importNode(AbstractImporter.java:44)
at com.atlassian.dbexporter.DbImporter.importData(DbImporter.java:69)
at com.atlassian.activeobjects.backup.ActiveObjectsBackup.restore(ActiveObjectsBackup.java:151)
at com.atlassian.jira.bc.dataimport.DefaultDataImportService.restoreActiveObjects(DefaultDataImportService.java:584)
at com.atlassian.jira.bc.dataimport.DefaultDataImportService.performImport(DefaultDataImportService.java:758)
at com.atlassian.jira.bc.dataimport.DefaultDataImportService.doImport(DefaultDataImportService.java:331)
at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:60)
at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:28)
at com.atlassian.jira.task.ImportTaskManagerImpl$TaskCallableDecorator.call(ImportTaskManagerImpl.java:157)
at com.atlassian.jira.task.ImportTaskManagerImpl$TaskCallableDecorator.call(ImportTaskManagerImpl.java:133)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2017-11-29 09:13:34,433 JiraImportTaskExecutionThread-1 WARN Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.p.d.dao.impl.CachingOrganizationDaoImpl] onImportCompleted - clearing cache !!
2017-11-29 09:13:34,507 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Importing data is 100% complete...
2017-11-29 09:13:34,507 JiraImportTaskExecutionThread-1 INFO Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] JIRA Data Import has finished.

And mayby this logs may be helpful too:

from plugin 'com.codebarrel.addons.automation'
com.querydsl.core.QueryException: Caught SQLServerException for delete from "dbo"."AO_589059_AUTOMATION_QUEUE"
where "AO_589059_AUTOMATION_QUEUE"."CLAIM_TIME" < ? and "AO_589059_AUTOMATION_QUEUE"."CLAIMANT" is not null
at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:50)
at com.querydsl.sql.Configuration.translate(Configuration.java:459)
at com.querydsl.sql.dml.SQLDeleteClause.execute(SQLDeleteClause.java:222)
at com.codebarrel.jira.plugin.automation.queue.JiraAutomationQueueStore.lambda$clearUnresolved$4(JiraAutomationQueueStore.java:158)
at com.codebarrel.data.api.jira.JiraDbConnectionManager.lambda$execute$0(JiraDbConnectionManager.java:34)
at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(DatabaseAccessorImpl.java:68)
... 2 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
at com.sun.proxy.$Proxy161.executeQuery(Unknown Source)
... 2 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208)
at com.sun.proxy.$Proxy2991.executeQuery(Unknown Source)
at com.codebarrel.data.api.jira.JiraDbConnectionManager.execute(JiraDbConnectionManager.java:32)
at com.codebarrel.jira.plugin.automation.queue.JiraAutomationQueueStore.clearUnresolved(JiraAutomationQueueStore.java:154)
at com.codebarrel.automation.api.queue.AutomationQueueImpl.clearUnresolved(AutomationQueueImpl.java:78)
at com.codebarrel.jira.plugin.automation.queue.JiraAutomationQueueLauncher.clearUnresolved(JiraAutomationQueueLauncher.java:60)
at com.codebarrel.jira.plugin.automation.queue.JiraAutomationQueueLauncher.stop(JiraAutomationQueueLauncher.java:54)
at com.codebarrel.jira.plugin.automation.event.EventRuleRegistryLauncher.onStop(EventRuleRegistryLauncher.java:81)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$5.consume(DefaultLifecycleManager.java:338)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$5.consume(DefaultLifecycleManager.java:333)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecyleAware(DefaultLifecycleManager.java:303)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyOnStopIfEnabled(DefaultLifecycleManager.java:332)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.access$100(DefaultLifecycleManager.java:49)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$1.evaluate(DefaultLifecycleManager.java:174)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$1.evaluate(DefaultLifecycleManager.java:171)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecycleAwares(DefaultLifecycleManager.java:258)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.onPluginFrameworkShuttingDown(DefaultLifecycleManager.java:170)
... 3 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:40)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:38)
at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:88)
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:204)
at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:115)
at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:83)
at com.atlassian.plugin.manager.DefaultPluginManager.broadcastIgnoreError(DefaultPluginManager.java:2129)
at com.atlassian.plugin.manager.DefaultPluginManager.shutdown(DefaultPluginManager.java:725)
at com.atlassian.jira.ComponentManager$PluginSystem.shutdown(ComponentManager.java:669)
at com.atlassian.jira.ComponentManager.stop(ComponentManager.java:324)
at com.atlassian.jira.upgrade.PluginSystemLauncher.stop(PluginSystemLauncher.java:147)
at com.atlassian.jira.startup.DefaultJiraLauncher.stop(DefaultJiraLauncher.java:213)
at com.atlassian.jira.startup.LauncherContextListener.contextDestroyed(LauncherContextListener.java:214)
... 5 filtered
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1535)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:467)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:409)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:219)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:199)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:356)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at com.querydsl.sql.dml.SQLDeleteClause.execute(SQLDeleteClause.java:208)
... 70 more

0 vote

The interesting parts of these logs to me is this:

2017-11-29 09:13:30,416 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:33,992 JiraImportTaskExecutionThread-1 ERROR Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.IllegalArgumentException: Unsupported field encountered: binary
java.lang.IllegalArgumentException: Unsupported field encountered: binary


That specific table 'AO_589059_AUTOMATION_QUEUE' is specifically created by the Automation Lite for Jira plugin 

Since you're seeing this error, it indicates that this plugin is not yet installed on this destination instance at the time of the restore.   As such, Jira can't create the table needed to store that plugin data and in turn we're seeing these SQL exceptions.   But my concern is that this error is a symptom of other plugins that might be missing or incompatible with this Jira.

You might need to update these plugins on the destination instance before the restore of the XML backup, otherwise the data might not be restored.   This tends to be easier to manage when you do the database migration as a separate process to the upgrade of Jira.  By both upgrading and migrating the database at the same time, this complicates the process needed in order to restore all the data in the XML backup properly.  


It is not to say it is impossible to both migrate and upgrade simultaneously, but in my experience it tends to be much easier when migrating everything (server, app, database, etc) like this to just follow these steps:

 

  1. install the same version of Jira on the destination instance,
  2. Connect this Jira instance to a new empty database using either the Jira Config Tool or by editing the dbconfig.xml
  3. copy the $JIRAHOME/plugins/installed-plugins/ folder from source to destination, also copy the $JIRAHOME/data into destination,
  4.  then restart the destination Jira once more to make sure this loads all your plugins.  When Jira starts up with an empty database, you will get the initial setup wizard where you can then use the 'import existing data' link to import your XML backup
  5. and then do the XML import in order to restore your data to this new database type.

Once this is done and working, then I would recommend upgrading Jira to the latest version.   

If you try to both upgrade and migrate these at the same time, the versions of your Jira plugins are unlikely to be compatible with this newer version of Jira and as such you would have to manually update each of these on the filesystem and restart Jira before doing this initial setup wizard where you can restore this.

Thanks for your answer. Today we are upgrading our production JIRA to newest version. Next step is to try migrate JIRA as you describe. I will let You know if we have succeeded.

Ok, so it doesn't work I did everything as it is written and it doesnt help. The same situation as it was before. Ale thing has been imported except boards and sprints. I will provide logs but insterting them there is not a best solution. Can i provide them to You in another way ?

Hi @Filip Gorloff,

I recreated a support request on your behalf for this issue.  Please upload the logs to this case:

https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-101918

From there we can take a closer look at what Jira is doing during this process.

Regards,
Andy

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

523 views 1 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you