Support Article
Alert DB Time for OOB SQL
SA-2788
Summary
A user that is monitoring PegaAES observes multiple warnings regarding a slow performing SQL statement. Specifically, the warning highlights a standard PRPC SQL statement, and occurs at regular intervals during the business day in the PROD environment.
Error Messages
No error messages in the Pega logfile; no error messages displayed on screen. However, PegaALERT logfile identifies the PEGA0005 alert against standard PRPC SQL. The SQL is too lengthy to list here (130 lines). However, the SQL appears to involve the following tables:
pr4_rule_vw
pr_sys_appcache_dep
pr_sys_app_ruleset_index
pr_sys_app_hierarchy_flat
Steps to Reproduce
No specific method of reproduction was identified. However, this issue appears every day in the PegaAES console.
Root Cause
Closer examination of the PegaALERT logfile reveals that this specific PEGA0005 alert is being caused by a small group of users (appr 2 users). Per the ALERT logfile, these two users have checked out rulesets (in PROD).
As per Pega Training: when a user has the right to check out rulesets, this places a greater load on the Rule Resolution process: Rules Resolution must identify rules that are eligible to be run from the user's ruleset list, and those rules that can be run from the user's PRIVATE (Checked Out) RuleSet list. Identifying rules in this manner places a much heavier burden on the PegaRULES database when identifying eligible rules to run.
Resolution
This issue is resolved through the following local change: Advised user to update their PROD environment, and deny the users the right to check out rules.
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.