Job execution lock has failed. PersistentJobExecutionFactory. ORA-00001. DuplicateKeyException

General
, , , , ,
1

Hi ,

I’m seeing the following exception in the logs for a Job scheduler. Though the job scheduler executing successfully but i could see this exception in the logs. I couldn;t trace it also. is it related to jvm or cluster side or nodes related exception? Kindly provide your inputs on this.

Exception :

2023-10-12 21:17:37,033 [BSCHEDULER_THREAD_10] [ STANDARD] ( JobSchedulerLifecycle) ERROR - [PersistentJobExecutionFactory] Job[abcdJS] execution lock has failed. com.pega.pegarules.pub.database.DuplicateKeyException: ORA-00001: unique constraint (ABCMS.PR_DATA_PK) violated DatabaseException caused by prior exception: java.sql.BatchUpdateException: ORA-00001: unique constraint (ABCMS.PR_DATA_PK) violated | SQL Code: 1 | SQL State: 23000 DatabaseException caused by prior exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (ABCMS

ORA-00001.png
ORA-00001.png1557×680 100 KB
.PR_DATA_PK) violated | SQL Code: 1 | SQL State: 23000 at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:448) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.store.ConnectionStatementStore.executeBatchForAllStatements(ConnectionStatementStore.java:233) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.store.ManagedTransaction.executeOutstandingBatches(ManagedTransaction.java:267) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:306) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:108) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.store.DataStoreManager.doInTransaction(DataStoreManager.java:273) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.UpdateProcessor.processUpdates(UpdateProcessor.java:226) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:756) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:1803) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:2943) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:2934) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:2924) ~[prprivate-data.jar:?] at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:2915) ~[prprivate-data.jar:?] at com.pega.platform.executor.jobscheduler.scheduler.internal.persistence.PersistentJobExecutionFactory$Execution.createExecution(PersistentJobExecutionFactory.java:517) ~[executor.jar:?] at com.pega.platform.executor.jobscheduler.scheduler.internal.persistence.PersistentJobExecutionFactory$Execution.getOrCreateExecution(PersistentJobExecutionFactory.java:216) ~[executor.jar:?] at com.pega.platform.executor.jobscheduler.scheduler.internal.persistence.PersistentJobExecutionFactory$Execution.lockAndGetJobExecution(PersistentJobExecutionFactory.java:127) ~[executor.jar:?] at com.pega.platform.executor.jobscheduler.sch

2

@Rajak9999 The ‘Job[abcdJS] execution lock has failed’ exception typically indicates that the job scheduler is unable to acquire a lock to execute the job. This could be due to a variety of reasons, including issues with the database or the job scheduler itself. It could be related to cluster or node issues, particularly if there are instabilities in the cluster. However, without more specific information about the exact circumstances and configuration of your system, it’s difficult to provide a definitive answer.

I would suggest that you log a ticket via the MSP so that our support team can help investigate the issue with you. Please provide the INC ticket reference here so that we can help track it.

3

Hi @MarijeSchillern ,

INC-A21455

Customer portal (pega.com).

Thanks
Raja

4

@Rajak9999 I can see that INC-A21455 has been resolved,.

GCS identified this is a custom job scheduler also the schema is not of Pega RULES or Pega DATA. As per the exception its coming from ABCMS schema.

As its a custom table Pega is unable to help on this issue. It needs to be sorted internally. It is probably not able to acquire lock. In the call you discussed the DB connection is getting timeout due to which the JS execution is getting failed.

You were asked to check with your DBA team and once the DB connection issues are sorted out it might resolve the JS issues.