Question
Vodafone
IN
Last activity: 24 Jun 2019 6:50 EDT
lot of PEGA0060 & PEGA0078 alerts observed in Production
Hi Team,
we are observing lot of PEGA0060 & PEGA0078 alerts in production.
PEGA0060 : Number of IH rows read above threshold :
Threshold :500 , Maximum value : 3200
PEGA0078 :composer shape is fetching around 2000 records which is normal.
Threshold : 500 Maximum value :3200
Addition information: Business requirement is to keep 90 days data in IH tables. we are afraid that the table may grow as we have 2 more months to reach 45 days
1.is there any work around to avoid this alert?
2. increasing threshold is good idea in this case? if yes, does it have any negative impact.
Please let me know if you have need any other information on this
Pegasystems Inc.
US
Hello!
I found a couple of articles that may be able to help you:
PEGA0060 alert: Number of Interaction History rows read above threshold
PEGA0078 alert: Number of records returned by the Compose shape is above threshold
Achmea
NL
Hi, we are experiencing the same, but I don't see andy issues in increasing the alert value.
It just causes less records to be written to the alert log.
Can anyobdy tell me how to increase this setting? Is it an DSS and how does it look?
Vodafone
IN
I beleive below are the dss
prconfig/alerts/dataflowmaxrowsincomposethreshold/default
prconfig/alerts/interactionreadrowsthreshold/default - but this is not working
can somebody confirm? also please confirm if there is no effect in increasing threshold to 3500 for both PEGA0060 & PEGA0078?
Pegasystems Inc.
IN
Hi,
The PEGA0060 alert is triggered when the number of Interaction History records retrieved for a customer or any other entity that is associated with a decision is above the threshold.
There is a table named PR_DATA_IH_FACT which contains transactional data that may grow fast.I believe high size of this table is generating this alert.You can check with your bussiness and keep only those data which is required.Generally we suggest to have 30 days data only.
Pega0078:The PEGA0078 alert is triggered when the number of records that are returned by a Compose shape in a particular data flow is above the threshold. The default value for the threshold is 250 records.. Too many records returned by the Compose shape can cause performance issues.
Hi,
The PEGA0060 alert is triggered when the number of Interaction History records retrieved for a customer or any other entity that is associated with a decision is above the threshold.
There is a table named PR_DATA_IH_FACT which contains transactional data that may grow fast.I believe high size of this table is generating this alert.You can check with your bussiness and keep only those data which is required.Generally we suggest to have 30 days data only.
Pega0078:The PEGA0078 alert is triggered when the number of records that are returned by a Compose shape in a particular data flow is above the threshold. The default value for the threshold is 250 records.. Too many records returned by the Compose shape can cause performance issues.
To eliminate this alert, check the join condition in the Compose shape for potential abnormalities and apply changes that are needed to reduce the number of records returned. If the condition is correct and the number of records can be accepted (they do not cause performance issues), consider increasing the threshold value for the alert. Increasing the heap size to accommodate for the increased number of records in memory is also an option to reduce performance issues
Thanks,
Abhinav
Vodafone
IN
Hi Abhinav,
Thanks for your detailed explaination. can you please bit elaborate more on below point?
"Increasing the heap size to accommodate for the increased number of records in memory is also an option to reduce performance issues"
we have 4-8 GB heap size and we are observing 3500 records max as threshold for PEGA0078 alerts. Please advise how we can gradually increase the size?
else should it be increased to 12GB?