Fixed
Details
Details
Priority
Affects versions
Fix versions
Components
Assignee
Earle Nietzel
Earle NietzelReporter
Jeffrey Miller
Jeffrey MillerLabels
Conversion Script Required
Yes
Created April 7, 2016 at 3:34 PM
Updated June 14, 2016 at 4:40 PM
Resolved April 8, 2016 at 11:29 AM
The quartz migration from 1.8 to 2.x required a lot of db changes that are documented on this page
http://www.quartz-scheduler.org/documentation/quartz-2.x/migration-guide
Also for creating quartz schema tables in a new install see:
https://github.com/quartz-scheduler/quartz/blob/master/distribution/src/main/assembly/root/docs/dbTables/tables_oracle.sql
I do see in their scripts they do not create the IS_UPDATE_DATA in a new install but is in the migration scripts.
I am leaning towards that the migration guide is wrong an should not have created
alter table qrtz_fired_triggers add column is_update_data bool;
2016-04-05 08:22:00,088 ERROR QuartzScheduler_QuartzSchedulerThread org.quartz.core.ErrorLogger - An error occurred while scanning for the next triggers to fire.
org.quartz.JobPersistenceException: Couldn't acquire next trigger: ORA-01400: cannot insert NULL into ("SAKAI04012016"."QRTZ_FIRED_TRIGGERS"."IS_UPDATE_DATA")
[See nested exception: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("SAKAI04012016"."QRTZ_FIRED_TRIGGERS"."IS_UPDATE_DATA")