Support Article
Upgrade failed due to IntegrityConstraintViolationException
SA-6167
Summary
User has started the upgrade.sh script and they receive an error in step 15: "Importing 15 of 52 : pxReporting_06.03.10.zip (Default Mode)"
As: "com.pega.pegarules.pub.database.IntegrityConstraintViolationException: Database-Saver-Insertfail"
Error Messages
[java] 2015-02-05 08:15:03,177 [your_hostname] [ STANDARD] [ ] ( internal.util.ImportImpl) ERROR - Save failed for 'RULE-OBJ-FIELDVALUE @BASECLASS PYCAPTION!CLICK HERE NAGEMENT REPORTS #20120713T021402.628 GMT'
[java] com.pega.pegarules.pub.database.IntegrityConstraintViolationException: Database-Saver-Insertfail
[java] From: (A88820BE3852741BFFA723A50145EDCE7)
[java] SQL: insert into pr4_fieldvalue (PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXHOSTID , PXINSID , PXINSNAME , PXINSTANCELOCKEDBY , PXINSTANCELOCKEDDATETIME , PXIHRONIZED , PXOBJCLASS , PXUPDATEDATETIME , PXUPDATEOPERATOR , PXUPDATEOPNAME , PXUPDATESYSTEMID , PYBASERULE , PYCIRCUMSTANCEDATE , PYCIRCUMSTANCEDATEPROP , PYCIRCUMSTANCEPROP , PYCIRCUMSTANCETYPE , PYCIRCUMELDNAME , PYFIELDVALUE , PYINTERFACE , PYLABEL , PYMETHODSTATUS , PYRULEAVAILABLE , PYRULEENDS , PYRULENAME , PYRULESET , PYRULESETVERSION , PYRULESTARTS , PYSORTDATECIRCUMWITHINRSMAJOR , PZRULESETVERSIONMAJZRULESETVERSIONPATCH , pzInsKey , pzPVStream) values (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?
[java] SQL Inserts: <2012-07-12 21:14:02.628> <nataa> <Abirami Natarajan> <sde> <fdbcd8ad50cff0a4882efb8d14381308> <!PYCAPTION!CLICK HERE TO ADD PRPC’S STANDARD WORK MANAGEMENT REPORTS> ERE TO ADD PRPC’S STANDARD WORK MANAGEMENT REPORTS> <<null>> <<null>> <<null>> <<null>> <Rule-Obj-FieldValue> <2012-07-12 12:08:23.617> <nataa> <Abirami Natarajan> <null>> <<null>> <<null>> <<null>> <@baseclass> <pyCaption> <Click here to add PRPC’s standard work management reports> <<null>> <Click here to add PRPC’s standard workl>> <Blocked> <<null>> <pyCaption Click here to add PRPC’s standard work management reports> <Pega-Reporting> <06-03-01> <<null>> <true> <6> <3> <1> <RULE-OTION!CLICK HERE TO ADD PRPC’S STANDARD WORK MANAGEMENT REPORTS #20120713T021402.628 GMT> <<stream>>
Steps to Reproduce
Run the upgrade.sh script with relevant DB details configured
Root Cause
An entry existing in the table pr4_fieldvalue with the same pxInsName existing in the table is observed. Upgrade was stopped abruptly in between and then started from afresh which created this entry in the table.
Resolution
User has delete this entry in the pr4_fieldvalue table corresponding to “RULE-OBJ-FIELDVALUE @BASECLASS PYCAPTION!CLICK HERE TO ADD PRPC’S STANDARD WORK MANAGEMENT REPORTS #20120713T021402.628 GMT” and resumed the upgrade process.
Published January 31, 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.