Related content:

Question pyCommitError: ORA-00001: unique constraint (DATAPEGA.PC_ASM_COBA83_WORK_PK) violated Question Getting ORA-00001: unique constraint violated when running install.sh Question ORA-00001: unique constraint PR_SYS_RULESET_INDEX_PK violated Question ORA-00001: unique constraint (PEGASA.PR_SYS_RULE_IMPL_PK) Discussion java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (ABC_RULES . PR_INDEX_REFERENCE_PK ) violated Question pyCommitError: Question Pega 7.3 Ignite : java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DATA_SCHEMA_USER.PRPC_IGNITE_SERVER_ADDR_PK) Question pyCommitError: (History-ABC-DEF-Work)** ORA-00904: "QUANTITYCONTRACT": invalid identifier Question unique constraint PEGA_RULES.PR_ASSEMBLEDCLASSES_PK violation error Discussion ORA-02443: Cannot drop constraint - nonexistent constraint
Contact a Moderator

Question

1
Replies
65
Views
BernadetaW Member since 2019 4 posts
Universitas Kristen Duta Wacana
Posted: 3 months ago
Last activity: 3 months 3 weeks ago

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 ?

 

Pega Platform 8.3.3 Case Management
Close popover
Posted: 3 months ago

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.
Share this page LinkedIn
Copied!