Support Article
No pr_sys_updatesCache record when saving D-A-DB-Table instance
SA-17403
Summary
When exposing a column to PRPC, you are making the SQL changes to the database table then saving the associated Data-Admin-DB-Table instance in one node. In Pega 7.1.6 this would add a pr_sys_updatescache instance record that would then be picked by the other nodes and processed. The other nodes would then start to see the new column as exposed and write to it.
After upgraded to Pega 7.1.8, this no longer works. The database changes are only picked up on the node that the Data-Admin-DB-Table instances was saved on. There is no pr_sys_updatescache instance record add saving a Data-Admin-DB-Table instance in Pega 7.1.8.
Error Messages
Not Applicable
Steps to Reproduce
1. Manually make SQL table changes
2. Save associated Data-Admin-DB-Table
Root Cause
A defect in Pegasystems’ code or rules. When moving database triggers to code in the engine level as part of Pega 7.1.8 enhancements, the update cache entries were not added for the following three classes:
- Data-Admin-DB-Table
- Data-Admin-DB-Name
- Data-Admin-DB-ClassGroup
Resolution
Apply HFix-24568.
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.