Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

IntegrityConstraintViolationException on cache table

SA-31692

Summary



Administrators observe numerous info messages in the Pega Platform logs coupled with IntegrityConstraintViolationExceptions occurring during the save of an entry into the pr_sys_cache_entry table.


Error Messages



2016-12-19 06:30:35,960 [ PegaRULES-Batch-4] [ STANDARD] [ PegaRULES:07.10] ( ) INFO - Database-Saver-Insertfail during operation: save entry for RULE-HTML-SECTION|WORK-!FLOWACTIONHTML_SIMPLE;STREAM|, com.pega.pegarules.pub.database.IntegrityConstraintViolationException: Database-Saver-Insertfail

From: (RequestorID:(Child Requestor))
SQL: insert into ID2XNPGB.pr_sys_cache_entry (PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXINSNAME , PXOBJCLASS , PZCACHECONFIGID , PZCLASS , PZCREATIONELAPSETIME , PZENTRYKEY , PZENTRYSOURCE , PZENTRYTYPE , PZEXPIRATIONTIME , PZIMPLEMENTATIONKEY , PZPACKAGE , PZPRIMARYPAGECLASSNAME , PZRULENAME , PZRULESETLISTHASH , PZRULETYPE , PZSEENBY , PZSHAREDRULESETLISTHASH , pzInsKey , pzPVStream) values (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)
...
Caused by SQL Problems.
Problem #1, SQLState 23505, Error code -803: com.ibm.websphere.ce.cm.DuplicateKeyException: AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE INDEX IN INDEX SPACE PRRSYSRC CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X'00001D8F01'.
Problem #2, SQLState 23505, Error code -803: com.ibm.db2.jcc.b.SqlException: AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE INDEX IN INDEX SPACE PRRSYSRC CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X'00001D8F01'.

Steps to Reproduce



Not Applicable


Root Cause



A defect in Pegasystems’ code or rules. This message is coupled to an expected condition and should not be pushed to the logs. The logic for trapping the message was updated to correct this behavior.

Resolution



Apply HFix-30899.
Suggest Edit

Published April 25, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us