Oracle Database error: "getBLOB not implemented for class oracle.jdbc.drive" after upgrade to JIRA 7

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

After upgrading from JIRA 6.4.x to JIRA 7, the following appears in the atlassian-jira.log

2015-10-19 15:03:38,317 localhost-startStop-1 ERROR [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.jira.event.ClearCacheEvent@50706103] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.jira.service.DefaultServiceManager.onClearCache(com.atlassian.jira.event.ClearCacheEvent), listener=com.atlassian.jira.service.DefaultServiceManager@586f0eae}] java.lang.RuntimeException: Error creating GenericValue (SQL Exception while getting value: (Invalid column type: getBLOB not implemented for class oracle.jdbc.driver.T4CLongRawAccessor))

Diagnosis

Environment

JIRA connected to supported Oracle database

Cause

There is inconsistency on column type for column PARAMETERS of the clusteredjob table which stores cron expression for JIRA 7.0+.

In JIRA 6.x, the column type is LONG RAW while in JIRA 7.x is BLOB

A bug report has been raised here -  JRA-47267 - Getting issue details... STATUS

Workaround

  1. Identify the latest XML backup from the $JIRA_HOME/export directory
  2. Create a new user as per the Connecting JIRA to Oracle guide
  3. Install a new JIRA 7.0.0 instance and connect it to the new Oracle user
  4. Import the XML backup

Last modified on Nov 1, 2018

Was this helpful?

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