Question
Cognizant
IN
Last activity: 25 Sep 2017 8:15 EDT
PEGA0004 CRITICAL ALERTS in development environment ; most of these alerts are triggered when we try to save-as an existing rule
We face severe latency in our development environment ( PRPC V 7.2.0 + ORA 11g + WAS 8.0 + AIX )
We heavily rely on branch rulesets to perform parallel development.
We have plenty of PEGA0004 CRITICAL ALERTS in our development environment and most of these alerts are triggered when we try to save-as an existing rule.
OOTB rule D_pzAvailableRuleSetsForRecord applied to class Rule-RuleSet-Name is the source of all these alerts.
***Moderator Edit: Vidyaranjan | Branched comment to create new thread***
Pegasystems Inc.
IN
Hi,
Refer the below link for details
https://docs-previous.pega.com/pega0004-alert-quantity-data-received-database-query-exceeds-limit
Try tracking it down based on it and provide more details.
Hi,
Refer the below link for details
https://docs-previous.pega.com/pega0004-alert-quantity-data-received-database-query-exceeds-limit
Try tracking it down based on it and provide more details.
Reason for the alert
Typically, this alert occurs when you work with lists of data by way of List View, Summary View, and Obj-List rules. For example, a database query might be trying to retrieve the entire BLOB (pzPVStream).
To learn what the system was trying to process when this alert was triggered, search the Alert log by using the time stamp and the message ID number for the full text of the message, which includes a stack trace. Locate the rules that caused this much data to be read. Remediation can include one or more of the following actions (depending on your requirements):
- Modify the report so that it retrieves only information from exposed columns, and does not need the BLOB column.
- Add more criteria.
- Limit the number of rows returned or reduce the number of data columns returned.
Thank You.
Cognizant
IN
Thanks for you response Shekhar. Your response is very valid in production environments where expensive reports are run.
The context is different here...
- PEGA0004 alerts are generated in development environment and not in production environment.
- Source of the alert is a OOTB pz rule (created and maintained by Pegasystems) and not a reporting rule created by us.
Pegasystems Inc.
IN
Hi,
Is there any particular step you are seeing which is creating an issue? If so try commenting it.
Also any fail message in tracer?
Thank You.
Cognizant
IN
We do not see any error messages in the designer studio.
What developers have observed so far is the extreme slowness or latency while saving us a rule.