After deployment to 8.1 Case Manager not loading properly
I performed an application deployment of an app that was built on 7.3. I then imported this onto a fresh install of 8.1. When I access the application the Case manager portal does not load properly. When trying to create a case within pega I receive the following error
pyCommitError:• ORA-00001: unique constraint (PEGA81DATA.PC_OV40E7_NJDEP_WORK_PK) violated
Does anyone have an idea what may be causing these issues???
Accepted Solution
Pegasystems Inc.
US
Truncate table got it.
Pegasystems Inc.
US
The ORA-00001 message is triggered when a unique constraint has been violated. Essentially the user causes the error when trying to execute an INSERT or UPDATE statement that has generated a duplicate value in a restricted field. The error can commonly be found when a program attempts to insert a duplicate row in a table.
When you create a case within pega, it inserts data into the "PC_OV40E7_NJDEP_WORK_PK" table under "PEGA81DATA" schema. A duplicate value in a restricted field is generated.
The ORA-00001 message is triggered when a unique constraint has been violated. Essentially the user causes the error when trying to execute an INSERT or UPDATE statement that has generated a duplicate value in a restricted field. The error can commonly be found when a program attempts to insert a duplicate row in a table.
When you create a case within pega, it inserts data into the "PC_OV40E7_NJDEP_WORK_PK" table under "PEGA81DATA" schema. A duplicate value in a restricted field is generated.
You can run the use case and collect the tracer log (check the DB query). The tracer log will tell where DB insertion gets failed.
Pegasystems Inc.
US
Does this mean that there is a duplicate value in the table? Or is there a duplicate property? would my solution be to delete the value from the table or will I have to redeploy. I created a product rule and included many classes maybe I added something twice.