SAP Knowledge Base Article - Preview

2917889 - SAP BPA by Redwood shows 'Startup Failure' after upgrade

Symptom

After upgrading BPA version, 'Startup Failed' message displayed when BPA URL is accessed.

Errors similar to the following can be seem in the default trace logs:

#2.0#2020 03 21 04:30:13:635#+00#Fatal#com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager#
#XX-PART-REDWOOD#redwood.com/redwood-automation-bpa-ear#C0000ABA410A002000000E3800011F35#243681550000001058#redwood.com/redwood-automation-bpa-ear#com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager#Guest#06B14907F6B2C11EA9F1500000E86490E#6b14907f6b2c11ea9f1500000e86490e0#Thread[Redwood Background Startup,5,Redwood]#Plain##
Not all components started successfully; stopping what was started.
[EXCEPTION]
JCS-112012: Cannot execute epoch initializer: com.redwood.scheduler.db.epoch.m33.M33InitializePublishService
at com.redwood.scheduler.db.DatabaseInitializer.initializeEpochs(DatabaseInitializer.java:1222)
at com.redwood.scheduler.db.DatabaseInitializer.initializeDatabase(DatabaseInitializer.java:780)
at com.redwood.scheduler.db.DatabaseInitializer.start(DatabaseInitializer.java:265)
at com.redwood.scheduler.lifecycle.impl.StartComponentVisitor.visit(StartComponentVisitor.java:34)
at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.visitAllComponents(DefaultComponentLifecycleManager.java:112)
at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:220)
at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:180)
at com.redwood.scheduler.lifecycle.impl.DefaultStartup.start(DefaultStartup.java:222)
at com.redwood.scheduler.lifecycle.impl.DefaultStartup$1.run(DefaultStartup.java:185)
at java.lang.Thread.run(Thread.java:836)
Caused by: JCS-122035: Unable to persist: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:1034)
at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:960)
at com.redwood.scheduler.db.DatabaseInitializer.initializeEpochs(DatabaseInitializer.java:1215)
... 9 more
Caused by: com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Unexpected exception during listener execution
at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.throwUnexpectedExceptionDuringListenerExecution(LowLevelPersistenceConfigurationImpl.java:663)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.informListeners(LowLevelPersistenceImpl.java:1013)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:318)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access$0(LowLevelPersistenceImpl.java:261)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteDirtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:121)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectList(LowLevelPersistenceImpl.java:184)
at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistence.writeDirtyObjectList(ClusteredLowLevelPersistence.java:67)
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:1009)
... 11 more
Caused by: java.lang.RuntimeException: Compiler component is not available
at com.redwood.scheduler.model.listeners.CompileListener$CompileTask.compile(CompileListener.java:1406)
at com.redwood.scheduler.model.listeners.CompileListener$CompileTask.compileInt(CompileListener.java:1390)
at com.redwood.scheduler.model.listeners.CompileListener$CompileTask.access$2(CompileListener.java:1388)
at com.redwood.scheduler.model.listeners.CompileListener$CompileTaskWorkUnit.compileAll(CompileListener.java:1944)
at com.redwood.scheduler.model.listeners.CompileListener.modelModified(CompileListener.java:506)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.informListeners(LowLevelPersistenceImpl.java:1002)
... 17 more

#2.0#2020 03 21 04:32:05:688#+00#Error#com.redwood.scheduler.persistence.persistence#
#XX-PART-REDWOOD#redwood.com/redwood-automation-bpa-ear#C0000ABA410A0023000003B70001304D#243681550000000943#redwood.com/redwood-automation-bpa-ear#com.redwood.scheduler.persistence.persistence#Guest#0##D75C10FA6B2C11EACB5A000D3AA90EE1#d75c10fa6b2c11eacb5a000d3aa90ee10#Thread[Redwood Background Startup,5,Redwood]#Plain##
SQL Error: SQLException (CODE=301, STATE=23000): [301]: unique constraint violated: Table(JCS_QUERYCOND0), Index(JCS_QUERYCOND00) with error: unique constraint violation for table SAPJAVA1:JCS_QUERYCOND0$delta_1$en, constraint='$uc_JCS_QUERYCOND00$', key value='9489', pos=0; indexname=JCS_QUERYCOND00
OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
[EXCEPTION]
com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: [301]: unique constraint violated: Table(JCS_QUERYCOND0), Index(JCS_QUERYCOND00) with error: unique constraint violation for table SAPJAVA1:JCS_QUERYCOND0$delta_1$en, constraint='$uc_JCS_QUERYCOND00$', key value='9489', pos=0; indexname=JCS_QUERYCOND00
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:1017)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:943)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1612)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:376)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:359)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:402)
at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeUpdate(PreparedStatementImpl.java:664)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.populateAndExecute(LowLevelPersistenceImpl.java:960)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.processCreation(LowLevelPersistenceImpl.java:823)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:357)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access$0(LowLevelPersistenceImpl.java:261)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteDirtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:121)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectList(LowLevelPersistenceImpl.java:184)
at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistence.writeDirtyObjectList(ClusteredLowLevelPersistence.java:67)
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:1009)
at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:960)
at com.redwood.scheduler.db.DatabaseInitializer.initializeEpochs(DatabaseInitializer.java:1215)
at com.redwood.scheduler.db.DatabaseInitializer.initializeDatabase(DatabaseInitializer.java:780)
at com.redwood.scheduler.db.DatabaseInitializer.start(DatabaseInitializer.java:265)
at com.redwood.scheduler.lifecycle.impl.StartComponentVisitor.visit(StartComponentVisitor.java:34)
at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.visitAllComponents(DefaultComponentLifecycleManager.java:112)
at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:220)
at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:180)
at com.redwood.scheduler.lifecycle.impl.DefaultStartup.start(DefaultStartup.java:222)
at com.redwood.scheduler.lifecycle.impl.DefaultStartup$1.run(DefaultStartup.java:185)
at java.lang.Thread.run(Thread.java:836)
Caused by: com.sap.db.jdbc.exceptions.SQLIntegrityConstraintViolationExceptionSapDB: [301]: unique constraint violated: Table(JCS_QUERYCOND0), Index(JCS_QUERYCOND00) with error: unique constraint violation for table SAPJAVA1:JCS_QUERYCOND0$delta_1$en, constraint='$uc_JCS_QUERYCOND00$', key value='9489', pos=0; indexname=JCS_QUERYCOND00
at com.sap.db.jdbc.exceptions.SQLExceptionSapDB._newInstance(SQLExceptionSapDB.java:163)
at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.newInstance(SQLExceptionSapDB.java:45)
at com.sap.db.jdbc.packet.HReplyPacket._buildExceptionChain(HReplyPacket.java:848)
at com.sap.db.jdbc.packet.HReplyPacket.getSQLExceptionChain(HReplyPacket.java:165)
at com.sap.db.jdbc.packet.HPartInfo.getSQLExceptionChain(HPartInfo.java:39)
at com.sap.db.jdbc.ConnectionSapDB._receive(ConnectionSapDB.java:4225)
at com.sap.db.jdbc.ConnectionSapDB.exchange(ConnectionSapDB.java:1665)
at com.sap.db.jdbc.PreparedStatementSapDB._execute(PreparedStatementSapDB.java:2873)
at com.sap.db.jdbc.PreparedStatementSapDB._execute(PreparedStatementSapDB.java:1993)
at com.sap.db.jdbc.PreparedStatementSapDB._executeUpdate(PreparedStatementSapDB.java:1968)
at com.sap.db.jdbc.PreparedStatementSapDB.executeUpdate(PreparedStatementSapDB.java:560)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPreparedStatement.java:108)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:373)
... 22 more


Read more...

Environment

SAP BPA by Redwood 9.0

SAP BPA by Redwood 9.1

Product

SAP Business Process Automation 9.0 by Redwood ; SAP Business Process Automation 9.1 by Redwood ; SAP NetWeaver 7.5

Keywords

Startup failed SAP Business Process Automation by Redwood upgrade , KBA , XX-PART-REDWOOD-BPA , SAP Business Process Automation by Redwood , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.