Related content:

Question

ORA-00001: unique constraint PR_SYS_RULESET_INDEX_PK violated

Question

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

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

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

Question

MARKETING DIRECTOR - segment creation is causing unique constraint violation in table STORED_FLD_TEMPL
Contact a Moderator

Question

5
Replies
1340
Views
Ganesh3185 Member since 2017 22 posts
Asurion
Posted: August 17, 2017
Last activity: September 6, 2017
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

Data Integration
Close popover
Moderation Team has archived post
Posted: 3 years ago

Hi Ganesh,


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


Thanks,


Habeeb Baig

Posted: 3 years ago

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

Posted: 3 years ago

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 .


 

Posted: 3 years ago

Thanks Gupta.  I will get back on this.


Thanks


Ganesh

Posted: 3 years ago

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