Support Article

Upgrade to 7.2.1 failing during updateDataRuleSummaryInstance

SA-29538

Summary



Upgrade from 7.1.9GA to 7.2.1 failing.


Error Messages



[java] 2016-10-14 12:05:41,520 [ main] [ ] [ ] ( internal.loaders.FastLoader) INFO - Performing Fast Deployment with Batch Enabled: true
[java] 2016-10-14 12:05:41,848 [ main] [ ] [ ] ( internal.util.MoveLog) INFO - Processed 129 of 814 (15.85%): 104 committed, 25 skipped, 0 seconds remaining
[java] 2016-10-14 12:05:41,879 [ main] [ ] [ ] ( internal.loaders.FastLoader) ERROR - 0 rows updated returned for instance of type Data-Rule-Summary with key RULE-DECLARE-PAGES D_FIELDNAMES #20131004T184959.439 GMT
[java] Oct 14, 2016 12:05:41 PM com.pega.pegarules.internal.bootstrap.PRBootstrap
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.PRException: PRException
[java] From: (unknown)
[java] at com.pega.pegarules.deploy.internal.loaders.UpgradeFastLoader.updateDataRuleSummaryInstance(UpgradeFastLoader.java:345)
[java] at com.pega.pegarules.deploy.internal.loaders.UpgradeFastLoader.updateInstance(UpgradeFastLoader.java:309)
[java] at com.pega.pegarules.deploy.internal.loaders.UpgradeFastLoader.importContents(UpgradeFastLoader.java:92)
[java] at com.pega.pegarules.deploy.internal.archive.importer.ArchiveImporterAbstract.importArchive(ArchiveImporterAbstract.java:46)
[java] at com.pega.pegarules.deploy.internal.archive.importer.Upgrader.handleArchive(Upgrader.java:154)
[java] at com.pega.pegarules.deploy.internal.archive.importer.AppBundleHandler.deploy(AppBundleHandler.java:90)
[java] at com.pega.pegarules.deploy.internal.archive.importer.Upgrader.runUpgrade(Upgrader.java:58)
[java] at com.pega.pegarules.deploy.external.util.UpgradeUtil.main(UpgradeUtil.java:73)

 

Steps to Reproduce



Run upgrade on the database to 7.2.1

Root Cause



A defect or configuration issue in the operating environment.  From database queries determined that there are rules in the pr4_rule_declarepages and pr4_rule_file_binary table which do not have the corresponding entry in the pr4_rule_vw table.

Resolution



Perform the following local-change: 

Queries such as this on each of the rule tables (pr4_base, pr4_rule, pr4_rule_property, etc.) will show if there is anything out of sync.  If the count is greater than 0 that indicates there are rules in that rule table which is not in the pr4_rule_vw table.   Change yourRulesSchema to the name of your rules schema.

select count(*) from yourRulesSchema.pr4_rule_file_binary rd where not exists (select pzinskey from yourRulesSchema.pr4_rule_vw vw where vw.pzinskey=rd.pzinskey); 
select count(*) from yourRulesSchema.pr4_rule_declarepages rd where not exists (select pzinskey from yourRulesSchema.pr4_rule_vw vw where vw.pzinskey=rd.pzinskey); 

For each table that was identified as being out of sync run insert statements like the following to add the missing rows with just the pzInskey column to the pr4_rule_vw table.  Change yourRulesSchema to the name of your rules schema.

insert into yourRulesSchema.pr4_rule_vw (pzinskey) (select pzinskey from yourRulesSchema.pr4_rule_file_binary rd where not exists (select pzinskey from yourRulesSchema.pr4_rule_vw vw where vw.pzinskey=rd.pzinskey));

insert into yourRulesSchema.pr4_rule_vw (pzinskey) (select pzinskey from yourRulesSchema.pr4_rule_declarepages rd where not exists (select pzinskey from yourRulesSchema.pr4_rule_vw vw where vw.pzinskey=rd.pzinskey));

Resume the upgrade.  After the upgrade is completed either from prpcUtils or from the portal resave the Rule-Declare-Pages and Rule-File-Binary rules so that the pr4_rule_vw table has all columns populated for these rules.
 

 

Published October 24, 2016 - Updated October 26, 2016


100% found this useful

Have a question? Get answers now.

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