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

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

 

Environment

Identity Governance 14.x

Cause

The QRTZ_SIMPLE_TRIGGERS 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 how many times the scheduler was triggered--resetting the value to 0 does not have any negative effects on the scheduled items. 

Other QRTZ tables might run into a similar situation.  Please examine other QRTZ tables as well

 

 

Resolution

In the table QRTZ_SIMPLE_TRIGGERS 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 that the QRTZ_SIMPLE_TRIGGERS table has a row for emailTrigger with TIMES_TRIGGERED = 9938419.

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

If the problem remains. It might be other QRTZ table columns having a similar situation

Examine the QRTZ tables' data: Once you identify the table and potential column, check the source data being inserted. Ensure the values fit within the target column's precision and scale definition

If the contents of the tables are not important.  You can clear up the tables and restart the Identity Governance Service

Example:

DELETE FROM QRTZ_SIMPLE_TRIGGERS;DELETE FROM QRTZ_SIMPROP_TRIGGERS;DELETE FROM QRTZ_CRON_TRIGGERS;DELETE FROM QRTZ_TRIGGERS;DELETE FROM QRTZ_JOB_DETAILS;