Question
1
Replies
181
Views
Universitas Kristen Duta Wacana
Posted: June 26, 2020
Last activity: June 27, 2020
pyCommitError: ORA-00001: unique constraint (DATAPEGA.PC_ASM_COBA83_WORK_PK) violated
I have a Case Types named Customer Care Benefit that have 5 Stages. I already make a sections and activities to Run this application. When I Run it, it was running well.
One day, I decided to Delete all Stages then Re-build the Stages again with the same name. Because I got some error at the first stages named Leader Acceptance and I cant resolve it. So I had delete that stage and build the stage again. It could saved as well.
But when I Run it, all flow and all stages looks like broken, The sections not available and I got error like this pyCommitError: ORA-00001: unique constraint (DATAPEGA.PC_ASM_COBA83_WORK_PK) violated (look at ScreenShot). I dont know how to fix this. Where I have to fix this error.
Can you guys tell me ?
Hi,
the error message indicates that from a DB perspective you try to insert or update a duplicate row:
It is noted here that ORA-00001 is common when: "a program tries to insert a "duplicate" row in a table," and that, "when a unique constraint is violated the row is NOT added to the table."
So it seems that your previous case hasn´t been removed properly. How did you remove it?
Here is a description on how to remove it properly: https://collaborate.pega.com/discussion/delete-case-type-pega7#:~:text=To%20remove%20the%20case%20type,listed%20in%20the%20Case%20Designer.