Invalid column type: getBLOB not implemented for class oracle.jdbc.driver.T4CLongRawAccessor during backup process

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.

 

Problem

When generating a backup, the following error is thrown in GUI

 

An exception occurred backing up: org.ofbiz.core.util.GeneralRuntimeException: Error creating GenericValue (SQL Exception while getting value: (Invalid column type: getBLOB not implemented for class oracle.jdbc.driver.T4CLongRawAccessor))

 

 

The following appears in the atlassian-jira.log

2016-09-13 13:24:21,066 http-bio-8747-exec-6 ERROR bostjanv 800x332x1 1oz48lq 172.22.48.96 /secure/admin/XmlBackup.jspa [web.action.util.XmlBackup] Exception occurred backing up: org.ofbiz.core.util.GeneralRuntimeException: Error creating GenericValue (SQL Exception while getting value:  (Invalid column type: getBLOB not implemented for class oracle.jdbc.driver.T4CLongRawAccessor))
org.ofbiz.core.util.GeneralRuntimeException: Error creating GenericValue (SQL Exception while getting value:  (Invalid column type: getBLOB not implemented for class oracle.jdbc.driver.T4CLongRawAccessor))
	at org.ofbiz.core.entity.EntityListIterator.next(EntityListIterator.java:253)
	at com.atlassian.jira.ofbiz.DefaultOfBizListIterator.next(DefaultOfBizListIterator.java:140)
	at com.atlassian.jira.ofbiz.WrappingOfBizListIterator.next(WrappingOfBizListIterator.java:80)
	at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntity(DefaultSaxEntitiesExporter.java:148)

Diagnosis

Environment

  • Oracle database

Diagnostic Steps

  • Enable the following debug class from logging and profiling: com.atlassian.jira.action.admin.export
  • Trace the following from the logs:
2016-09-13 14:07:08,114 http-bio-8747-exec-24 DEBUG bostjanv 844x393x1 1oz48lq 172.22.48.96 /secure/admin/XmlBackup.jspa [action.admin.export.DefaultSaxEntitiesExporter] curEntityName = OSPropertyData
2016-09-13 14:07:08,114 http-bio-8747-exec-24 DEBUG bostjanv 844x393x1 1oz48lq 172.22.48.96 /secure/admin/XmlBackup.jspa [action.admin.export.DefaultSaxEntitiesExporter]   inTransaction=true

 

  • Check from JIRA_Installation/WEB-INF/classes/entitydefs/entitymodel.xml for OSPropertyData from above curEntityName = OSPropertyData
  • You will see the following from the entitymodel.xml file:

        <entity entity-name="OSPropertyData" table-name="propertydata" package-name="">
            <field name="id" type="numeric"/>
            <field name="value" col-name="propertyvalue" type="blob"/>
            <prim-key field="id"/>
        </entity>

     


     

  • This will show the expected table type for the table

  • Crosscheck with the table in database

    SQL> desc propertydata;
     Name					   Null?    Type
     ----------------------------------------- -------- ----------------------------
     ID					   NOT NULL NUMBER(18)
     PROPERTYVALUE					    LONG RAW

Cause

There are tables in JIRA which does not have the correct type, where in above case, the expected is 'blob' but the table is having 'long raw'. Can be due to manual intervention or wrong configuration of the database.

Resolution

Alter the table type accordingly like below example:

SQL> alter table propertydata modify (propertyvalue BLOB);
…
SQL> desc propertydata;
 Name					   Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID					   NOT NULL NUMBER(18)
 PROPERTYVALUE					    BLOB
Last modified on Sep 29, 2016

Was this helpful?

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