Discussion
Accenture
IN
Last activity: 6 Apr 2018 19:26 EDT
Invalid Triggers - after Upgrade
After upgrade is done, from 6.x to 7.1.8,
I can see some triggers in Data schema are in invalid state, those are below
TRPR4_BASE
TRPR4_FIELDVALUE
TRPR4_REQ
TRPR4_RRS
TRPR4_RULE
TRPR4_RULE_AUTOTEST
TRPR4_FLOW
TRPR4_PROP
TRPR4_RULE_SHORTCUT
TRPR4_USE
I have seen this all the time I did upgrade.
is this normal and having no impact? or we need to do manual re-compile again for this Trigger.
Regards
Shankha
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accenture
IN
please explain what you mean by "we need not to run additional triggers starting ML8." ?
what to run, how to run? where to get additional scripts?
Regards
Shankha
Morgan Stanley
GB
Hi,
Our team is seeing similar issues with triggers once migrated to 7.1.8
What does "not to run" them mean? Can we safely delete them? In our case, all the triggers are in INVALID state. Both in data and rules schema
Thanks
Peter
Pegasystems Inc.
IN
After the upgrade run the System->Database->Optimize Schema wizard for dropping all the unused tables from data schema. this will automatically delete all the triggers from your data schema.
Thanks,
Dhev
Pegasystems Inc.
US
Starting in 7.1.8, you should drop these triggers as they are no longer required for Pega7 to operate, and in fact would impact the operation of Pega7.
In 7.1.7 and previous releases these triggers were used to maintain the pr4_rule_vw table, which is the used to list all Rule instances that exist, and the pr_updatescache table which is used by the system pulse to ensure all running nodes have the latest Rule changes.
In 7.1.8 the logic was moved into the Pega7 java engine for usability and maintenance purposes, and therefore these triggers should not exist to in order to avoid duplicate effort and possible data corruption.