Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Ganesh Kumar CV (GaneshKumarC3200)
Virtusa UK Ltd

Virtusa UK Ltd
GB
GaneshKumarC3200 Member since 2020 31 posts
Virtusa UK Ltd
Posted: Aug 17, 2017
Last activity: Sep 6, 2017
Posted: 17 Aug 2017 1:13 EDT
Last activity: 6 Sep 2017 0:55 EDT
Closed

ORA-00001: unique constraint (PEGASA.PR_SYS_RULE_IMPL_PK)

Hi

I am seeing an error ORA-00001: unique constraint (PEGASA.PR_SYS_RULE_IMPL_PK) after a connect-soap call fired though a datapage. Can anyone please help to understand why this error occurs?

Version - 7.1.9

Thanks

Ganesh

To see attachments, please log in.
Data Integration

Posted: 7 years ago
Posted: 17 Aug 2017 6:46 EDT
Habeeb Baig (BaigHabeeb)
Virtusa IT Consulting
Lead Decisioning Architect
Virtusa IT Consulting
AE

Hi Ganesh,

Please check If you have duplicate values in db table which you may be referring during the soap call.

Thanks,

Habeeb Baig

To see attachments, please log in.
Posted: 7 years ago
Posted: 4 Sep 2017 5:31 EDT
Ganesh Kumar CV (GaneshKumarC3200)
Virtusa UK Ltd

Virtusa UK Ltd
GB

Hi Habeeb - Thanks for the response. Above is a pega internal caching table.I think this error occurs when the data page results are attempted to cached. Its still happening sporadically.

 

Thanks

Ganesh

To see attachments, please log in.
Posted: 7 years ago
Posted: 4 Sep 2017 8:36 EDT
Abhinav Gupta (Abhinav7)
PEGA
Manager, Technical Support - Platform Service Engineering
Pegasystems Inc.
IN

Hi Ganesh,

Could you please provide complete stack of the error.

The root cause of this error is below

"pzInsKey" is a primary key column of table "pr_sys_rule_impl",During execution of this connect soap call It is trying to insert a value which is already present in this column as a result this issue is reported.

Please share the complete stack trace so that we can verify  the existence of value in DB .

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 6 Sep 2017 0:55 EDT
Ganesh Kumar CV (GaneshKumarC3200)
Virtusa UK Ltd

Virtusa UK Ltd
GB

Hi - For the past two days, I could not locate this error again. For now, please consider this as closed and I will re-post it with full trace once i am able to find it again. Thanks for the help.

 

Thanks

Ganesh

To see attachments, please log in.

Related content:

Question

ORA-00001: unique constraint PR_SYS_RULESET_INDEX_PK violated

Question Solved

Getting ORA-00001: unique constraint violated when running install.sh

Discussion

java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (ABC_RULES . PR_INDEX_REFERENCE_PK ) violated

Question

pyCommitError: ORA-00001: unique constraint (DATAPEGA.PC_ASM_COBA83_WORK_PK) violated

Question

pyCommitError: ORA-00001: unique constraint (DATAPEGA.PC_ASM_COBA83_WORK_PK) violated

Question Solved

Pega 7.3 Ignite : java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DATA_SCHEMA_USER.PRPC_IGNITE_SERVER_ADDR_PK)

Discussion

ORA-02443: Cannot drop constraint - nonexistent constraint

Question

unique constraint PEGA_RULES.PR_ASSEMBLEDCLASSES_PK violation error

Discussion

Frequent "duplicate key value violates unique constraint" error in the database

Discussion

java.sql.SQLException: ORA-02443: Cannot drop constraint - nonexistent constraint

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice