Support Article

Poor Performance of Scheduled Reports



The limit for the Property Reference cache was previously increased to 1,000,000 for the system. However, one particular scheduled report is still triggering numerous PEGA0017 alerts. This report has 77 columns and typically contains about 60,000 rows. It is exported to Excel for distribution to the recipients.

Error Messages

2016-11-02 14:37:43,643 GMT*8*PEGA0017*30000*30000*a94bef516b2dc3620bcd24db08c8ae55*NA*NA*HDE57E9F67D10F07FEDC65517E779EE20*EVOC FileServiceAdmin*BAC-GBAM-Work*GBAM:01.01.01*ea4f2f87ee3153515f6e3690756e4075*Y*51*HDE57E9F67D10F07FEDC65517E779EE20*7*WebContainer : 0*TABTHREAD1**(...)|nnn.nnn.nn.nn*Activity=ShowStream*Rule-Obj-Activity:ShowStream*RULE-OBJ-REPORT-DEFINITION PZCREATEEXPORTDATA #20140903T071016.942 GMT Step: 1 Circum: 0------pxTotalReqTime=106.69;pxInteractions=1;pxAlertCount=119;pxRulesUsed=166;pxRunStreamCount=287,145;pxOtherIOElapsed=0.14;pxRulesExecuted=41;pxInputBytes=1,723;pxTrackedPropertyChangesCount=1;pxRuleCount=8;pxDBInputBytes=116,088;pxRDBIOCount=1;

Steps to Reproduce

Create a large scheduled report that creates an Excel report, and sends out an email that has a link to this Excel report.

Root Cause

During the export to Excel process, this report generates additional 1,600,000 unique property references.


Perform the following local-change:

Increase the limit for the Property Reference cache to more than 1,600,000. If excessive numbers of PEGA0017 alerts are still generated, continue to increase the limit until the number of alerts drops to five or six alerts per day.

Use an alternate method to generate and export the report, like BIX, if increasing the size of the cache has negative impact on the system's performance or if the number of alerts cannot be reduced.

Published January 19, 2017 - Updated February 10, 2017

Have a question? Get answers now.

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