Question
Facing Rule sync issue
We have multiple nodes connecting to same DB, each node have separate PegaTempDir and pointed to same DB so sharing same Temporary Cache tables. But when users in one node make changes other nodes are not reflecting the change, we have to clear cache everytime to reflect rule change. Please someone give solution to this issue. We recently upgraded to 7.17.
- Can you check if system pulse is running on all your nodes? You can use the SMA for that.
- Are the triggers in the database defined on all rule tables enabled?
Rajiv Nistala can you help me how we can identify whether the triggers are enable on all rule tables. we ran in to the similar issue on 7.17 Pega Multinode environment in the recent past and trying to delete the extract files and restart nodes but it didnot help. in our case the system pulse is running on all nodes.
Did you take a look at this issue - Re: Changes in one node is not reflected in another
Yes Rajiv Nistala but the fix suggested is for Pega 7.1.6 and 7.1.7 . we are on Pega 7.1.8 and we dont have the triggers installed in DB and from the PDN article below i understand that there will be no DB triggers supported by Pega.
https://pdn.pega.com/release-note/startup-check-removes-custom-db-triggers
Please suggest appropriate solution.
There is another scenario I am aware of, if a node does not start clean, then system pulse may not work. Check the clipboard to see if pxSystemNodeStatus = 'Unknown'. If that is the case, please create a SR with GCS for further investigation.
Sorry about that. From your initial post I was given to understand that you upgraded to 7.1.7 and thus I provided that link. With 7.1.8, there are no rule table triggers in the database. You should check what Kevin Zheng has suggested.