Troubleshooting
Problem
This exception is from the Quartz Scheduler driver, which is the library the
schedulerapp uses to manage triggering jobsThis error means that the Quartz driver is failing to execute it’s queries due to a mismatch between the query and the expected DB schema of it’s scheduler.QRTZ* tables.
This error can happen when the Quartz driver is configured for the wrong backend SQL database type via the
org.quartz.jobStore.driverDelegateClassproperty:By default, SCH assumes MySQL is the backend DB, so there is no need to override this property if you are using MySQL as your SCH’s SQL DB.
However, if your SCH instance is connecting to a PostgresSQL DB, then you’ll need to override this value by configuring
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.PostgreSQLDelegateso that the Quartz driver can send the correct SQL queries for PostgresSQL databases.
Symptom
When starting Control Hub, an exception is thrown which causes the SCH process to crash:
Abnormal exit: java.lang.RuntimeException: java.lang.RuntimeException: Could not start Quartz scheduler: org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn't retrieve trigger: Bad value for type long
Resolving The Problem
To fix this error for an SCH using PostgresSQL, uncomment this line in $DPM_CONF/scheduler-app.properties to specify the property driver class:
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
Restart SCH and this DB exception should be resolved.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
15 March 2025
UID
ibm17186144