ORA-00932 SQL exception on Jira DVCS connector

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

When trying to connect Jira using Oracle database with a self-managed Gitlab or Github through DVCS connector the test connection fails with ORA-00932: inconsistent datatypes: expected - got CLOB  on "AO_E8B6CC_REPOSITORY_MAPPING" table.

Environment

Jira version <8.19 running Oracle 19c database

Diagnosis

The following message will be displayed on the atlassian-jira.log:

2021-09-02 14:35:25,071-0600 DVCSConnector.MessageExecutor:thread-3 ERROR tib2tib 875x2036x1 aaaaa x.x.x.x /rest/bitbucket/1.0/repository/10/softsync [c.a.j.p.d.service.message.MessageConsumer] Synchronization failed: 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
    	- minor version:0
    	- major version:19
[...]
java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB
[...]
Caused by: Error : 932, Position : 333, Sql = SELECT "FORK_OF_SLUG","FORK_OF_OWNER","SMARTCOMMITS_ENABLED","DELETED","LOGO","SLUG","ACTIVITY_LAST_SYNC","NAME","FORK_OF_NAME","LINKED","LAST_CHANGESET_NODE","REMOTE_ID","REPOSITORY_URL","UPDATE_LINK_AUTHORISED","ID","ORGANIZATION_ID","LAST_COMMIT_DATE","FORK" FROM "AO_E8B6CC_REPOSITORY_MAPPING" WHERE "ORGANIZATION_ID" = :1   AND "REPOSITORY_URL" = :2   AND "DELETED" = :3  , OriginalSql = SELECT "FORK_OF_SLUG","FORK_OF_OWNER","SMARTCOMMITS_ENABLED","DELETED","LOGO","SLUG","ACTIVITY_LAST_SYNC","NAME","FORK_OF_NAME","LINKED","LAST_CHANGESET_NODE","REMOTE_ID","REPOSITORY_URL","UPDATE_LINK_AUTHORISED","ID","ORGANIZATION_ID","LAST_COMMIT_DATE","FORK" FROM "AO_E8B6CC_REPOSITORY_MAPPING" WHERE "ORGANIZATION_ID" = ?  AND "REPOSITORY_URL" = ?  AND "DELETED" = ? , Error Msg = ORA-00932: inconsistent datatypes: expected - got CLOB


Cause

Known bug, no workarounds available.

Solution

Bug fixed in Jira 8.19.1 and later releases.

Last modified on Nov 26, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.