Jira Data Center database import fails due to missing tables from JCMA plugin

Related content

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Jira Data Center database import fails due to missing tables from Jira Cloud Migration Assistant plugin

Diagnosis

The following errors can be found in the atlassian-jira.log during database import on Jira Data Center: 

2022-02-10 13:09:38,279-0800 pool-51-thread-7 ERROR      [c.a.j.m.tracking.utils.ThreadUtils] uncaught exception in periodic executor
com.atlassian.cache.CacheException: com.querydsl.core.QueryException: Caught PSQLException for select "MIGRATION"."MIGRATION_ID", "MIGRATION"."PLAN_ID", "MIGRATION"."START_MIGRATION_CONTEXT_JSON", "MIGRATION"."IN_PROGRESS_STATUS_JSON", "MIGRATION"."OUTCOME_JSON", "MIGRATION"."APP_OUTCOME_JSON", "MIGRATION"."STARTED_BY", "MIGRATION"."CREATED_TIMESTAMP", "MIGRATION"."UPDATED_TIMESTAMP" from "public"."AO_6FF49D_MIGRATION_ENTITY" "MIGRATION" where "MIGRATION"."OUTCOME_JSON" is null and "MIGRATION"."UPDATED_TIMESTAMP" > ?
...
Caused by: org.postgresql.util.PSQLException: ERROR: relation "public.AO_6FF49D_MIGRATION_ENTITY" does not exist

Checking the destination database, the tables will be present as expected

As the import fails during the Active Objects import step, other AO tables may fail to restore the data.

Cause

The cause is not known yet. 

Solution

  1. Remove the Jira Cloud Migration Assistant plugin on both source and destination Jira instances
  2. Perform a new Jira database export on the source instance;
  3. Perform a new Jira database import on the destination instance;


How to Remove the JCMA app
  1. Stop the Jira application.
  2. Navigate to <jira_install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins path.
  3. Locate JCMA plugin (plugin name will be like jira-migration-plugin-1.4.4.jar - version number of jar file could be different on your Jira).
  4. Remove this plugin from <jira_install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins path. (You can place the JCMA jar in another "temp" folder outside the Jira Installation dir).
  5. If you have upgraded the bundled JCMA plugin, you may also need to navigate to the path <jira_home>/plugins/installed-plugins (or <jira_shared_home>/plugins/installed-plugins in a clustered Jira Data Center environment) and repeat steps 3 and 4.
  6. Let's clear the plugin cache.

    Clear the following plugin cache files:

    • Delete the <jira_home>/plugins/.bundled-plugins directory (this will be regenerated on restart)
    • Delete the <jira_home>/plugins/.osgi-plugins directory (this will be regenerated on restart)
    • Delete the contents of <jira_install>/work directory (just the contents, not the folder itself)
    • Delete the contents of <jira_install>/temp directory (just the contents, not the folder itself)
  7. Start the Jira application.


Also see: MIG-740 - JCMA (Jira Cloud Migration Assistant) plugin may prevent JIRA from starting correctly


Last modified on Nov 27, 2024

Was this helpful?

Yes
No
Provide feedback about this article

Related content

Powered by Confluence and Scroll Viewport.