Blank Health Check page after upgrading Jira Data Center to v10.3.x or ATST version 2.13.x
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
The Health Check page in Jira appears blank after upgrading Jira Data Center to v10.3 or updating the Atlassian Troubleshooting and Support Tools to v2.13 or later.
Diagnosis
After upgrading, you would see a blank Health Check page under System > Troubleshooting and Support Tools.
You will observe an error in the atlassian-jira.log, regarding the Atlassian Troubleshooting and Support Tools app failing to start due to a database schema conflict with an error "
column being added already exists in table".
2026-03-25 22:39:51,607-0300 JIRA-Bootstrap ERROR [c.a.t.d.f.systemevents.persistence.SystemEventsStoreImpl] Failed to store system event
java.util.concurrent.ExecutionException: com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.troubleshooting.plugin-jira]
at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2096)
at io.atlassian.util.concurrent.Promises$OfStage.get(Promises.java:357)
at com.atlassian.activeobjects.osgi.ActiveObjectsDelegate$2.awaitInitialization(ActiveObjectsDelegate.java:174)
at com.atlassian.troubleshooting.dcdp.features.systemevents.persistence.SystemEventsStoreImpl.getInitializedAO(SystemEventsStoreImpl.java:149)
at com.atlassian.troubleshooting.dcdp.features.systemevents.persistence.SystemEventsStoreImpl.lambda$storeSystemEvent$2(SystemEventsStoreImpl.java:91)
at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:21)
at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:49)
at jdk.internal.reflect.GeneratedMethodAccessor294.invoke(Unknown Source)
.....
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:Oracle
- version:Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.30.0.0.0
- minor version:30
- major version:19
Driver:
- name:Oracle JDBC driver
- version:23.2.0.0.0
java.sql.SQLException: ORA-01430: column being added already exists in table
at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:55)
at com.atlassian.troubleshooting.dcdp.transfer.data.cache.ao.AODataCacheSchemaFixUpgradeTask.upgrade(AODataCacheSchemaFixUpgradeTask.java:27)
at com.atlassian.troubleshooting.upgrade.AODataCacheSchemaFixUpgradeTaskProxy.upgrade(AODataCacheSchemaFixUpgradeTaskProxy.java:48)
at com.atlassian.activeobjects.internal.TimedActiveObjectsUpgradeTask.upgrade(TimedActiveObjectsUpgradeTask.java:42)
at com.atlassian.activeobjects.internal.ActiveObjectUpgradeManagerImpl.lambda$upgrade$0(ActiveObjectUpgradeManagerImpl.java:73)
at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:21)
at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:49)
.....
Caused by: Error : 1430, Position : 42, SQL = ALTER TABLE "AO_4789DD_DCDP_HI_CACHE" ADD "EMAN_CIRTEM" VARCHAR(255), Original SQL = ALTER TABLE "AO_4789DD_DCDP_HI_CACHE" ADD "EMAN_CIRTEM" VARCHAR(255), Error Message = ORA-01430: column being added already exists in table
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:710)Cause
This issue is related to a new AO table AO_4789DD_DCDP_HI_CACHE that is used as a local cache for data being sent to Cloud as part of the Portfolio Insights feature, provided by the ATST plugin.
The AODataCacheSchemaFixUpgradeTask attempts to add the EMAN_CIRTEM column to the AO_4789DD_DCDP_HI_CACHE table. If a previous upgrade attempt was interrupted (often by an OutOfMemory error), the column may already exist, causing error: "java.sql.SQLException: column being added already exists in table"
Additionally, if this table contains a high volume of rows, it can lead to memory exhaustion during the migration process.
Solution
To resolve the blank Health Check page and ensure the plugin initializes correctly, you must clear the affected table and remove the redundant column so the upgrade task can complete cleanly. Truncating the AO_4789DD_DCDP_HI_CACHE table alone will not resolve the issue.
Stop the Jira application.
Perform a full backup of your database.
Run the following SQL commands on your database to truncate the data and drop the conflicting column. The query below works in Oracle. Please modify it as per your database:
-- Truncate the table to resolve potential memory exhaustion TRUNCATE TABLE "AO_4789DD_DCDP_HI_CACHE"; -- Drop the column that is causing the schema conflict ALTER TABLE "AO_4789DD_DCDP_HI_CACHE" DROP COLUMN "EMAN_CIRTEM";Delete the .bundled-plugins and .osgi-plugins directories located within JIRA_HOME/plugins/.
Start Jira.
You may encounter OutOfMemoryError during the upgrade or after the upgrade to v10.3.x or v11.3.x due to a bug with ATST plugin. Here are the bugs that are currently reported:
Was this helpful?