Failure in restoring a backup of 7.x to 8.3.1

[FL Sysadmin]

Hi! i was about to upgrade my 7.13.1 to the latest 8.3.1 Linux version. I ran into some issues during import, and probably(?) because of that some of the data is not working so i went back to old version until we get this solved.

My first attempt to upgrade failed because of the charset, so i made a new DB, and the restored the XML backup i had.

The error i see in SQL log was:

< 2019-08-13 15:31:34.123 EEST >ERROR: duplicate key value violates unique constraint "AO_575BF5_DEV_SUMMARY_pkey"
< 2019-08-13 15:31:34.123 EEST >DETAIL: Key ("ID")=(1) already exists.
< 2019-08-13 15:31:34.123 EEST >STATEMENT: INSERT INTO public."AO_575BF5_DEV_SUMMARY" ("CREATED", "ID", "ISSUE_ID", "JSON", "PROVIDER_SOURCE_ID", "UPDATED") VALUES ($1, $2, $3, $4, $5, $6)

and in GUI all i got was this:

There was a problem restoring ActiveObjects data for the plugin Atlassian Jira - Plugins - Development Integration Plugin(com.atlassian.jira.plugins.jira-development-integration-plugin) #5.5.0 plugin. Importing table AO_575BF5_DEV_SUMMARY failed. Please check the log for details.

Other issues after this was that my Scrum board didn't allow me to end the running sprint (could not find entity of type interface com.atlassian.greenhopper.service.sprint.SprintAO with key 157), so i couldn't start a new one either, and some other errors as well which i didn't document properly :)

Any ideas?

[Andy Heinzer · Accepted solution]

Sorry to hear about this error.  It certainly sounds like the restore process failed in this SQL exception, which could cause other data to fail to import as well. 

It's difficult to say the cause for this.  It could be that the database has not been setup exactly per Connecting Jira applications to a database, or that the database in use is not listed in the supported platforms for that version of Jira, OR it could be that the XML backup itself has some level of corruption/bad data in it.   If you are confident that the first two possibilities have been ruled out, then it likely stands that the backup has a duplicate record for that table in the database.

If you have a different backup file you could use, that might be a better alternative here.

However if not, then you could extract the active-objects.xml file from that backup.zip.   It is possible to open this file in a text editor, or grep for this specific table name, "AO_575BF5_DEV_SUMMARY".  It might be possible for you to make an adjustment directly to this file to remove/alter the duplicate record in this XML format, then save that file, and add it back to a zip along with the entities.xml file to make a zip file that can be imported without error.

This is not always successful (sometimes another table then has another error), but I have seen it work before.   If you're unsure what might need to change in that file, try posting here with some of the search results and perhaps I can better guide you on changes to that file that you could make to try to work past this restore/import problem.

Andy

[FL Sysadmin]

Thanks Andy! We can actually close this case, with some trial + error routines i was able to restore the XML to a new Jira instance successfully, it took almost an hour but i haven't had any issues afterwards. Maybe the first XML indeed had some error in it.