Support Article
Sporadic Integrity Constraint Violation exceptions in DB2
SA-22059
Summary
Integrity Constraint Violation exceptions appear in the PegaRULES log intermittently. HFIX-9952 does not resolve the issue.
Error Messages
2016-02-08 19:09:25,808 [ WebContainer : 4] (he.appcentric.AppEntryBaseImpl) INFO your_id|127.0.0.1 - Database-Saver-Insertfail during operation: save entry for RULE-HTML-SECTION|YOUR_RULE;STREAM|PegaRULES!07.10$f1f96fcf4bd589e2672087c710748e09, com.pega.pegarules.pub.database.IntegrityConstraintViolat
ionException: Database-Saver-Insertfail
From: (H7265968EB7203B0AADFEE7C203E4A1AD:127.0.01)
SQL: insert into PROD.pr_sys_appcache_entry (PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXINSNAME , PXOBJCLASS , PZAPPHASH , PZAP
PNAME , PZAPPVERSION , PZASPECT , PZCACHECONFIGID , PZCLASS , PZCONTEXTPATHHASH , PZCREATIONELAPSETIME , PZENTRYKEY , PZENTRYSOURCE , PZEXPIRATIONTIME , PZIMPLEMENTATIO
NKEY , PZPACKAGE , PZPRIMARYPAGECLASSNAME , PZQUALIFIEDRULENAME , PZRULENAME , PZRULETYPE , PZSAFETOINFER , pzInsKey) values (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?
, ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)
SQL Inserts: <2016-02-08 19:09:25.659> <your_id> <your_name - Production> <58f8555b292f73eaca8d4339d5df9ddd> <RULE-HTML-SECTION!YOUR_RULE!07.10$F1F96FCF4BD589E2672087C710748E09!1292740085!F59DD4147C7B60952E4BE40663702BF8> <System-AppCentric-Cache-Entry> <PegaRUL
ES!07.10$f1f96fcf4bd589e2672087c710748e09> <PegaRULES> <07.10> <Stream> <1292740085> <ra_stream_pzruleformparametersscript_680f6956eb90a0df3fd12375ee
f71c14.class> <f59dd4147c7b60952e4be40663702bf8> <0.722> <RULE-HTML-SECTION|YOUR_RULE;STREAM|PegaRULES!07.10$f1f96fcf4bd589e2672087c710748
e09> <<null>> <2016-02-08 19:11:55.874> <html_section.ra_stream_pzruleformparametersscript_680f6956eb90a0df3fd12375eef71c14> <com/pegarules/generated
/html_section> <Rule-> <YOUR_RULE> <YOUR_RULE> <Rule-HTML-Section> <true> <SYSTEM-APPCENTRIC-CACHE-ENTRY RULE-HTML
-SECTION!YOUR_RULE!PEGARULES!07.10$F1F96FCF4BD589E2672087C710748E09!1292740085!F59DD4147C7B60952E4BE40663702BF8>
Caused by SQL Problems.
Problem #1, SQLState 23505, Error code -803: com.ibm.websphere.ce.cm.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;PROD.PR_SYS_APPCACHE_ENTRY
Problem #2, SQLState 23505, Error code -803: com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;PROD.PR_SYS_APPCACHE_ENTRY
Steps to Reproduce
Not Applicable.
Root Cause
A defect in Pegasystems’ code or rules. For DB2 PegaRULES database, the sporadic error is not suppressed correctly although the presence of error in log file does not indicate any issue with the application.
Resolution
This issue is scheduled to be resolved in future Pega 7.2 update release.
Published April 13, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.