Support Article

Getting PEGA0005 alerts due to OOTB activities/rules at runtime

SA-32463

Summary



In the application alert logs file , most of the PEGA0005 alerts are generating due to OOTB standard pega rules like (pr4_rules and other tables) while getting data from the pega DB. 

Error Messages



Alerts in Pega Alert log file.

Steps to Reproduce



Not Applicable

Root Cause



A defect or configuration issue in the operating environment, behaviour was initially reported with Pega0005 alerts with an impression as this be the root cause for the slowness. However by going through alert logs, Pega0037 was the actual reason found and rest of Pega0005 alerts were getting printed because of consequences since there were lot of cache misses which caused the rules/data to get picked from database not from the cache. 

Resolution



Run static assembler and refer to the PDN article https://pdn.pega.com/pega0037-alert-rule-assembly-time-exceeded-threshold/pega0037-alert-rule-assembly-time-exceeded 
 

Published January 13, 2017 - Updated January 24, 2017


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.