SQL exception in the logs when upgrading Jira Service Management on an Oracle database.

XMLWordPrintable

    • 13
    • Severity 2 - Major
    • 83

      Issue Summary

      During a Zero Downtime Upgrade from Jira Service Management an SQL error may appear in the atlassian-jira.log file, indicating inconsistent data types in the Oracle database table AO_8542F1_IFJ_OBJ_ATTR_VAL. This error is logged while performing an upgrade task for the com.riadalabs.jira.plugins.insightplugin.

      This could be a blocker for customers if they are planning to upgrade using ZDU as the status remains in upgrade mode only because the UPGRADE_TASKS fails in ZDU.

      Please note that this is not limited to ZDU only but even relates to regular upgrade even for non-clustered instance when using Oracle database

      Below is the detailed error snippet:

      2026-04-09 14:35:24,611+0000 Caesium-1-3 ERROR [c.a.upgrade.core.DefaultUpgradeTaskFactoryProcessor] Upgrade task [com.riadalabs.jira.plugins.insight, buildNumber=97] failed  
com.atlassian.activeobjects.internal.ActiveObjectsSqlException:  
There was a SQL exception thrown by the Active Objects library:  
Database: Oracle 19c, Driver: Oracle JDBC 19.12.0.0.0  
Caused by: java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB  
	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.find(EntityManagedActiveObjects.java:153)
	at com.riadalabs.jira.plugins.insight.services.core.dal.dao.impl.InsightActiveObject.find(InsightActiveObject.java:100)
	at com.riadalabs.jira.plugins.insight.upgrade.AssetsUpgradeTask097.cleanupEmptyTextareaValues(AssetsUpgradeTask097.kt:62)
	at com.riadalabs.jira.plugins.insight.upgrade.AssetsUpgradeTask097.runUpgrade(AssetsUpgradeTask097.kt:53)
	at com.atlassian.upgrade.core.DefaultUpgradeTaskFactoryProcessor.runOneUpgradeTask(DefaultUpgradeTaskFactoryProcessor.java:109)
	...
Caused by:  
Error : 932, Sql = SELECT ... FROM "AO_8542F1_IFJ_OBJ_ATTR_VAL" WHERE "TEXT_VALUE" = ?,  
Error Msg = ORA-00932: inconsistent datatypes: expected - got CLOB  
	at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:513)
	...
2026-04-09 14:35:24,640+0000 Caesium-1-3 WARN [c.a.upgrade.core.DefaultUpgradeTaskFactoryProcessor] Failed to complete upgrade task [factory=com.riadalabs.jira.plugins.insight, buildNumber=97]
2026-04-09 14:35:24,642+0000 Caesium-1-3 ERROR [c.a.jira.upgrade.UpgradeScheduler] Error occurred during execution of upgrades  
com.atlassian.jira.upgrade.UpgradeException: Plugin upgrade(s) failed  
	at com.atlassian.jira.upgrade.UpgradeScheduler.runPluginUpgrades(UpgradeScheduler.java:111)
	at com.atlassian.jira.upgrade.UpgradeScheduler.runUpgrades(UpgradeScheduler.java:82)
	...

      Steps to Reproduce

      1. Install JSM v11.3.3 using Oracle database.
      2. Upgrade JSM from v11.3.3 to v11.3.4.
      3. Monitor the atlassian-jira.log file for com.riadalabs.jira.plugins.insightplugin plugin upgrade tasks.

      Expected Results

      The upgrade tasks for {{com.riadalabs.jira.plugins.insight }}plugin should be completed successfully.

      Actual Results

      The upgrade tasks for com.riadalabs.jira.plugins.insight }}plugin are throwing the {{java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB exception in the atlassian-jira.log file.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Gabriel Riera
              Reporter:
              Ankit Pruthi
              Votes:
              6 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: