Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Rule base inconsistencies observed in a multi node system

SA-17200

Summary



Rule base inconsistencies observed in a multi node system. The same rule differs when opened on different nodes. Abnormal size of the pr_sys_updatescache table has been observed.
 

Error Messages



Not applicable.


Steps to Reproduce



Not applicable.


Root Cause



The issue was caused by different time zones used in the database and in the application server. This led the sppr_sys_updatescache_gettime stored procedure to return incorrect time to the System Pulse activity which was not able to operate correctly. The issue can be identified by raising to DEBUG the logging level for the logger "com.pega.pegarules.data.internal.access.DatabaseImpl.SystemPulse" and manually execute the SystemPulse activity 2015-11-26 16:36:56,670 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   - Starting System Pulse
2015-11-26 16:36:56,671 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   - nodePZInsKey = ...
2015-11-26 16:36:56,671 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   - Calling gettime stored procedure
2015-11-26 16:36:56,672 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   - Last index or pulse time: 2015-11-26 10:35:56.368
2015-11-26 16:36:56,672 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   -     Current database time: 2015-11-26 10:36:56.671
2015-11-26 16:36:56,672 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   -     Reading pulse records up to time: 2015-11-26 10:36:56.671
2015-11-26 16:36:56,673 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) INFO    - Number of updated items since last index or pulse: 0
2015-11-26 16:36:56,673 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   - Updating last pulse time to time 2015-11-26 10:36:56.671
2015-11-26 16:36:58,970 [...] [  STANDARD] [ ] [...] (ccess.DatabaseImpl.SystemPulse) DEBUG   - System Pulse Complete.


The former logs show a 6 hours negative gap between the database time returned by the stored procedure and the application server time determined by the log time stamps.

Resolution



Perform the following local-change: As explained in the Pega 7.1.8 Platform Installation Guide for Websphere on Oracle
https://pdn.pega.com/documents/pega-718-installation-guide-for-websphere-on-oracle

Configure your database server, application server, and the system on which you are running the installation to use the same: 
  1. Time zone 
  2. Character encoding (UNICODE or EBCDIC)
  3. Regional settings/locale
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us