Unable to start application: org.quartz.JobPersistenceException: Couldn't recover jobs: Couldn't store trigger: ORA-01438: value larger than specified
search cancel

Unable to start application: org.quartz.JobPersistenceException: Couldn't recover jobs: Couldn't store trigger: ORA-01438: value larger than specified

book

Article ID: 230686

calendar_today

Updated On:

Products

CA Identity Governance CA Identity Manager CA Identity Suite

Issue/Introduction

The application does not start. The application server log shows the following ORA-01428 error.


ERROR [org.springframework.web.context.ContextLoader] (ServerService Thread Pool -- 74) Context initialization failed: org.springframework.context.ApplicationContextException: Failed to start bean 'quartzScheduler'; nested exception is org.springframework.scheduling.SchedulingException: Could not start Quartz Scheduler; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn't recover jobs: Couldn't store trigger: ORA-01438: value larger than specified precision allowed for this column

 

Cause

The QRTZ_SIMPLE_TRIGGERED table has a column named TIMES_TRIGGERED that supports a maximum value of 9,999,999.

Setting the value in the table to 0 resets the counter.

This is just a counter of the number of times the scheduler was triggered--resetting the value to 0 does not have any negative effects on the scheduled items. 

 

 

Resolution

In the table QRTZ_SIMPLE_TRIGGERED check for any rows where the TIMES_TRIGGERED column is close to 9,999,999. 

Then update any such rows to 0.

For example,

you notice in the QRTZ_SIMPLE_TRIGGERED table that it has a row for emailTrigger with TIMES_TRIGGERED = 9938419.

In the above case, you will update the QRTZ_SIMPLE_TRIGGERED table and set TIMES_TRIGGERED column to 0 for the emailTrigger row.

For further assistance with the table update, please contact your Database Administrator.