Oracle Database error: "getBLOB not implemented for class oracle.jdbc.drive" after upgrade to JIRA 7
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
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-47267Getting issue details... STATUS
Workaround
- Identify the latest XML backup from the $JIRA_HOME/export directory
- Create a new user as per the Connecting JIRA to Oracle guide
- Install a new JIRA 7.0.0 instance and connect it to the new Oracle user
- Import the XML backup