BW Process chain restart failed processes

[former_member237959]

Hi All,

Whenever we try to restart only the failed processes of a process chain which is in Console state, CPS job is getting failed with the below error message. But the failed processes are restarted and successful in the BW system. Please help.

An error has occurred in the SAP connector: JCS-122035: Unable to persist: JCS-102200: Job 108708 (submitted from SAP_CcmsJob copy from 2015/02/26 13:54:24,218 America/New_York) already exists
Details:
JCS-122035: Unable to persist: JCS-102200: Job 108708 (submitted from SAP_CcmsJob copy from 2015/02/26 13:54:24,218 America/New_York) already exists
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:941)
at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:882)
at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:3)
at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:43)
at com.redwood.scheduler.connector.sap.rfc.job.bw.restart.ProcessChainRestart.restart(ProcessChainRestart.java:326)
at com.redwood.scheduler.connector.sap.rfc.service.operation.OperatorReplyOperation.doWork(OperatorReplyOperation.java:63)
at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:38)
at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:76)
at java.lang.Thread.run(Thread.java:763)
Caused by: com.redwood.scheduler.model.exception.UniqueConstraintViolatedException: JCS-102200: Job 108708 (submitted from SAP_CcmsJob copy from 2015/02/26 13:54:24,218 America/New_York) already exists
at com.redwood.scheduler.model.ModelSQLExceptionMappingImpl.wrapUniqueConstraintViolatedException(ModelSQLExceptionMappingImpl.java:29)
at com.redwood.scheduler.persistence.helper.OracleSQLExceptionWrapper.wrapSQLException(OracleSQLExceptionWrapper.java:39)
at com.redwood.scheduler.persistence.helper.SAPSQLExceptionWrapper.wrapSQLException(SAPSQLExceptionWrapper.java:55)
at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper.wrapSQLException(RecoverySQLExceptionWrapper.java:51)
at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.rethrowException(OuterPersistenceUnitOfWorkManager.java:91)
at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.execute(OuterPersistenceUnitOfWorkManager.java:43)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectList(LowLevelPersistenceImpl.java:160)
at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistence.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90)
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:920)
... 8 more
Caused by: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.JCS_JOB0B) violated

OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:125)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1544)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:376)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:354)
at com.sap.sql.jdbc.common.CommonPreparedStatement.execute(CommonPreparedStatement.java:867)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.execute(PreparedStatementWrapper.java:360)
at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.execute(PreparedStatementImpl.java:432)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.populateAndExecute(LowLevelPersistenceImpl.java:906)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.processModificationIfPossible(LowLevelPersistenceImpl.java:701)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:292)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access$0(LowLevelPersistenceImpl.java:164)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteDirtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103)
at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.execute(OuterPersistenceUnitOfWorkManager.java:38)
... 11 more
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.JCS_JOB0B) violated

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1046)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3613)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3694)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1354)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPreparedStatement.java:108)
at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Oracle11gPreparedStatement.java:167)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:373)

Regards,

Lohit

[gmblom]

Hello,

I think you have ran into a known issue, or your chain is using custom process types that are not implemented correctly.

Which CPS version are you on?

Regards Gerben

[former_member237959]

Hello Geben,

We are on M33.104.

Regards,

Lohit

[gmblom]

Hello,

There have been some fixes in this area in M33.116. But I cannot 100% guarantee that it will fix this particular issue.

To be sure just open up an OSS ticket to investigate.

Regards Gerben

[former_member237959]

Thank you Gerben. We will do the same.

Regards,

Lohit