Workflow Notification Will Not Start After Cloning (Doc ID 278127.1)

Last updated on MAY 03, 2016

Applies to:

Oracle Workflow - Version 11.5.9 to 11.5.10.2 [Release 11.5 to 11.5.10]
Information in this document applies to any platform.
Checked for relevance on 06-APR-2013


Symptoms

After cloning, the workflow notification mailer on the new target Instance will not start. Following error is found in the FNDCPGSC*.txt files:

...
LOG_ID_UNKNOWN :
oracle.apps.fnd.cp.gsc.SvcComponentContainer.getNewWorkflowContext() : BEGIN
Could not start Service Component Container because an unexpected RuntimeException or other Throwable occurred

java.lang.NoClassDefFoundError: oracle/jdbc/driver/OraclePreparedStatement
java.lang.NoClassDefFoundError: oracle/jdbc/driver/OraclePreparedStatement
at oracle.apps.fnd.wf.apps.ContextFactory.makeContext(ContextFactory.java:50)
at oracle.apps.fnd.wf.common.WorkflowContext.<init>(WorkflowContext.java:76)
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.getNewWorkflowContext(SvcComponentContainer.java:919)
at oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer.initializeStateMachine(GSMSvcComponentContainer.java:170)
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.start(SvcComponentContainer.java:513)
at oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer.main(GSMSvcComponentContainer.java:271)

...

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms