JIRA Upgrade from Versions 3.9 or Below Fails due to Database Schema Change
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Symptoms
If using the Alternative method of upgrading JIRA rather than the recommended method from a version prior to JIRA 3.9, the upgrade may fail with the following error message:
1
2
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, trigger_id, cronExperssion FROM qrtz_cron_triggers (Invalid column name 'cronExperssion'.)
Cause
This occurs due to database schema changes in JIRA 3.9.
Resolution
There are two solutions to this problem:
Use the recommended method to upgrade.
If unable to use the XML backup, modify the database schema directly:
1 2 3mysql> alter table qrtz_cron_triggers drop column CRON_EXPERSSION; mysql> ALTER TABLE qrtz_cron_triggers ADD cronExperssion varchar(255);
Was this helpful?