Exception occurs and Pega 7.4 update fails
SqlIntegrityConstraintViolationException occurs and Pega 7.2.2 update to Pega 7.4 fails. Additionally, the PreBuild conclusions did not work.
[java] com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: Error for batch element #54: AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE INDEX IN INDEX SPACE PR4R1B4M CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X'00000AF801'.
Steps to Reproduce
Run the Migrate scripts.
A defect or configuration issue in the operating environment.
Some residual rows caused duplicate pzInskeys.
The PreBuild conclusions did not work due to missing truncate privilege on PR_SYS_UPDATESCACHE.
Perform the following local-change:
Identify stale or duplicate pzInskeys from pr4_rule_vw and other pr4_rule* tables and delete them.
Perform the below steps to Bypass the update cache for the PreBuild conclusions:
- Set bypass.truncate.updatescache=true in the setupDatabase.properties.
- Allow the upgrade to resume.
- After the upgrade completes, manually run the TRUNCATE TABLE <schema>.PR_SYS_UPDATESCACHE SQL before deploying the Pega application archive.
Published March 1, 2019 - Updated December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.