Solving Error Quartz and Pentaho BI Server CE 4.8.0


Installing Pentaho BI Server 4.8.0 over MySQL shows the error below on pentaho.log file :

ERROR [org.quartz.core.ErrorLogger] An error occured while scanning for the next trigger to fire.org.quartz.JobPersistenceException: Couldn’t acquire next trigger: Field ‘PRIORITY’ doesn’t have a default value
[See nested exception: java.sql.SQLException: Field ‘PRIORITY’ doesn’t have a default value]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1778)
at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1218)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
* Nested Exception (Underlying Cause) —————
java.sql.SQLException: Field ‘PRIORITY’ doesn’t have a default value
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)

ERROR [org.quartz.core.ErrorLogger] An error occured while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Couldn’t acquire next trigger: Field ‘PRIORITY’ doesn’t have a
default value [See nested exception: java.sql.SQLException: Field ‘PRIORITY’ doesn’t have a default value]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1778)
at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1218)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
* Nested Exception (Underlying Cause) —————
java.sql.SQLException: Field ‘PRIORITY’ doesn’t have a default value
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
To solve this errors execute the SQL code below

<br />ALTER TABLE  QRTZ_TRIGGERS DROP COLUMN PRIORITY<br />ALTER TABLE  QRTZ_FIRED_TRIGGERS DROP COLUMN PRIORITY<br />
Advertisements

2 thoughts on “Solving Error Quartz and Pentaho BI Server CE 4.8.0

  1. Dropping the column? Thats a bit brutal, does the underlying ORM layer re-create it with the right options then? I found it easier simply to set the DEFAULT of the column to 0

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s