ORA-00932: inconsistent datatypes: expected - got CLOB - ATST

XMLWordPrintable

    • 10.03
    • 13
    • Severity 2 - Major
    • 87

      Here is the issue :

      com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
	- name:Oracle
	- version:Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production
Version 19.29.0.0.0
	- minor version:29
	- major version:19
Driver:
	- name:Oracle JDBC driver
	- version:23.26.0.0.0
java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB
https://docs.oracle.com/error-help/db/ora-00932/
...
com.atlassian.troubleshooting.dcdp.transfer.data.cache.ao.AODcdpDataPersistenceServiceImpl.delete(AODcdpDataPersistenceServiceImpl.java:114)
	at com.atlassian.troubleshooting.dcdp.transfer.data.cache.PersistentDcdpDataCache.clear(PersistentDcdpDataCache.java:64)
	at com.atlassian.troubleshooting.dcdp.transfer.data.cache.ConfigurableDcdpDataCache.clear(ConfigurableDcdpDataCache.java:74)
	at com.atlassian.troubleshooting.dcdp.transfer.data.collector.DcdpDataCollector.clearOutdatedCacheEntries(DcdpDataCollector.java:52)
	at com.atlassian.troubleshooting.dcdp.transfer.data.collector.DcdpDataCollector.collectMultiplePerBatchData(DcdpDataCollector.java:48)
....
Caused by: java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB
https://docs.oracle.com/error-help/db/ora-00932/
...
Caused by: Error : 932, Position : 44, SQL = DELETE FROM "AO_4789DD_DCDP_HI_CACHE" WHERE "NODE_ID" = :1 AND "COLLECTION_TIMESTAMP" < :2 , Original SQL = DELETE FROM "AO_4789DD_DCDP_HI_CACHE" WHERE "NODE_ID" = ? AND "COLLECTION_TIMESTAMP" < ?, Error Message = ORA-00932: inconsistent datatypes: expected - got CLOB

      This issue is related to a new AO table used as a local cache for data being sent to Cloud as part of the Portfolio Insights/Instance Optimization feature, provided by the ATST plugin :

      [Setting up Data Center for instance optimization | Portfolio insights Cloud | Atlassian Support|https://support.atlassian.com/portfolio-insights/docs/setting-up-jira-data-center-for-instance-optimization/]

      The AO cache is intended to support caching and sending large quantities of data than the previous in-memory version.

      It has occurred because the default “string” implementation in AO in Oracle defaults to a CLOB. The column needs a max string length restriction to enforce the use a CHAR type column.

      Workaround : 

      For now it is possible to disable the use of the AO cache by using the feature flag :

      com.atlassian.troubleshooting.data.cache.ao.disabled

      Please refer to the following documentation to add this feature flag/ dark feature : [Manage dark features in Jira Data Center | Jira and Jira Service Management | Atlassian Support|https://support.atlassian.com/jira/kb/manage-dark-features-in-jira-data-center/]

              Assignee:
              Unassigned
              Reporter:
              Samuel de Azevedo Dias
              Votes:
              7 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: