I have seen this problem before. It has been a couple of years but if I recall correctly, it is due to the unique constraint (BMPTPRCSSMT_AK1X) on table BAM_PT_PROCESS_META. The constraint is on columns PROCESS_NAME and PROCESS_VER. However, PROCESS_NAME is not the fully qualified name of the process model (PROCESS_EXT_ID is). In our case, the issue happened because two different developers had created processes with the same name but under different projects.
My suggestion to you: query the BAM_PT_PROCESS_META table to get an understanding of why the unique constraint is being violated. You may learn that the record that exists there is old and needs to be cleaned up, for example, by deleting the process from MWS and then redeploying the new one. Or, you may learn that the record that exists there is for a valid and active process. In that case, I would recommend renaming the process you’re attempting to deploy now. Based on the constraint, you could also simply change the process version, but it’s not as clean as renaming it.
I believe this issue has been addressed in more recent versions. When I get a chance, I’ll check that unique index on my 9.x databases and I’ll get back with you.
Percio
#webMethods-BPMS#MWS-CAF-Task-Engine#webMethods