SQLServerException: Invalid object name after upgrade to 8.16.1

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。

要約

After upgrading to Jira 8.16.1, the logs are reporting the error:

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'null.AO_6FF49D_MIGRATION_ENTITY

環境

  • Jira 8.16.1
  • MS SQL Server

診断

  • No schema is defined in the <jira-home>/dbconfig.xml file.
  • The full stack trace is found in the <jira-home>/log/atlassian-jira.log:
[c.a.j.m.tracking.utils.ThreadUtils] uncaught exception in periodic executor
com.atlassian.cache.CacheException: com.querydsl.core.QueryException: Caught SQLServerException for select "MIGRATION"."MIGRATION_ID", "MIGRATION"."PLAN_ID", "MIGRATION"."START_MIGRATION_CONTEXT_JSON", "MIGRATION"."IN_PROGRESS_STATUS_JSON", "MIGRATION"."OUTCOME_JSON", "MIGRATION"."STARTED_BY", "MIGRATION"."CREATED_TIMESTAMP", "MIGRATION"."UPDATED_TIMESTAMP" from "null"."AO_6FF49D_MIGRATION_ENTITY" "MIGRATION" where "MIGRATION"."OUTCOME_JSON" is null and "MIGRATION"."UPDATED_TIMESTAMP" > ?
...
Caused by: com.querydsl.core.QueryException: Caught SQLServerException for select "MIGRATION"."MIGRATION_ID", "MIGRATION"."PLAN_ID", "MIGRATION"."START_MIGRATION_CONTEXT_JSON", "MIGRATION"."IN_PROGRESS_STATUS_JSON", "MIGRATION"."OUTCOME_JSON", "MIGRATION"."STARTED_BY", "MIGRATION"."CREATED_TIMESTAMP", "MIGRATION"."UPDATED_TIMESTAMP" from "null"."AO_6FF49D_MIGRATION_ENTITY" "MIGRATION" where "MIGRATION"."OUTCOME_JSON" is null and "MIGRATION"."UPDATED_TIMESTAMP" > ?
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'null.AO_6FF49D_MIGRATION_ENTITY'.

原因

This table AO_6FF49D_MIGRATION_ENTITY is used by the Jira Cloud Migration Assistant for migrating between Server and Cloud instances. Jira 8.16.1 in particular may have some issues with the schema missing specifically for this AO table.

Atlassian recommends to create a new schema for the Jira tables, otherwise the instance may face further issues.

If the schema is missing altogether, it is absolutely critical that it is specified otherwise it will cause significant problems with the JIRA instance.

ソリューション

Follow the steps in the KB article Change the schema name for Jira database tables.


最終更新日 2021 年 11 月 30 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.