Oracle Workflow Internal Forced termination Error

Question

We will appreciate if anyone can be of assistance in helping us with a problem we are experiencing with Oracle Workflow.
We have an Oracle Workflow Task which has several activities.
This exact version of the Workflow works in 2 other environments, with the exception of the current environment where we are experiencing the issue described below.
1.     The Oracle Workflow Task is submitted via the Oracle Workflow monitor: Launch Processes
2.     The Task terminates internally immediately after submission ***
3.     The report result status on the first activity indicates “Force”
4.     The overall Workflow reports result status indicates “Failure”
5.     The first activity normally executes for 12 minutes before executing the next activity, we can see the process executing on the database level (Performing database steps as expected – logging to an audit table 6 times)
6. The follow on activity never gets executed.
We believe that this is an environment issue. Out application stack is:
1.     Oracle Database 9.2.0.5
2.     Oracle Workflow 2.6.2
3.     Oracle warehouse builder 10g R2
Thanks for any help in resulving this.

Answer 1

Hi,
We have just had a similar problem, also when trying to deploy a process flow module.
After investigating the contents of the WF_ITEM_TYPES table we noticed that an entry allready existed with the same Name as the Process Flow Module that we were trying to deploy.
To fix this we simply renamed the Mapping and reran the deployment, with sucess.
We belive that a previous failed deployment of the Process Flow Module (due to a missing language), left the Database in an inconsistent state, renaming the flow meant that the PK was no longer broken, however the half finished deployment has probably left further rubish in the system.... we will see :-)