DB Bytes Read (PEGA 0004) Critical Alert --------> 7.1.8
Pega0004 critical Alerts are coming in alert logs.
Description:The number of database bytes input for this interaction has exceeded the WARNING level for Requestor HB7158403A32F62A44E021BE0047462E0, operator cjyothi Maximum bytes: 5000000 Actual bytes: 5556815
Pega Stack:
>> Property-Set;RULE-OBJ-ACTIVITY WORK- GETATTACHMENTREFERENCE #20150806T173755.381 GMT Step: 10 Circum: 0;doActivity Rule-Obj-Activity:GetAttachmentReference;initial Executable;0 additional frames in stack;
>> Obj-Open-By-Handle;RULE-OBJ-ACTIVITY WORK- OPEN #20150306T061357.865 GMT Step: 7 Circum: 0;doActivity Rule-Obj-Activity:Open;java;RULE-OBJ-ACTIVITY @BASECLASS DOUIACTION #20150515T115751.633 GMT Step: 24 Circum: 0;2 additional frames in stack;
>>Looks like first stack trace was occurred due to the utility function( @pxHaveAttachmentSpecificAccess(myStepPage, "pyAllowViewAll") ) is being invoked at step#10 of GetAttachmentReference activity,
I see the PDN has suggested a local change to resolve this issue on (https://pdn.pega.com/support-articles/seeing-pega0004-when-user-accesses-attachments-list) , and it's for 6.2 version but Is the issue still persist on 7.1.8 version too?
Pega0004 critical Alerts are coming in alert logs.
Description:The number of database bytes input for this interaction has exceeded the WARNING level for Requestor HB7158403A32F62A44E021BE0047462E0, operator cjyothi Maximum bytes: 5000000 Actual bytes: 5556815
Pega Stack:
>> Property-Set;RULE-OBJ-ACTIVITY WORK- GETATTACHMENTREFERENCE #20150806T173755.381 GMT Step: 10 Circum: 0;doActivity Rule-Obj-Activity:GetAttachmentReference;initial Executable;0 additional frames in stack;
>> Obj-Open-By-Handle;RULE-OBJ-ACTIVITY WORK- OPEN #20150306T061357.865 GMT Step: 7 Circum: 0;doActivity Rule-Obj-Activity:Open;java;RULE-OBJ-ACTIVITY @BASECLASS DOUIACTION #20150515T115751.633 GMT Step: 24 Circum: 0;2 additional frames in stack;
>>Looks like first stack trace was occurred due to the utility function( @pxHaveAttachmentSpecificAccess(myStepPage, "pyAllowViewAll") ) is being invoked at step#10 of GetAttachmentReference activity,
I see the PDN has suggested a local change to resolve this issue on (https://pdn.pega.com/support-articles/seeing-pega0004-when-user-accesses-attachments-list) , and it's for 6.2 version but Is the issue still persist on 7.1.8 version too?
>> Second stack trace was occurred while reading BLOB column of a object in a single interaction,which has more than 50 MB . Is it suggestible to increase value of below env variable ? if yes then what would be the feasible value to set up?
alerts/database/interactionByteThreshold/warnMB (Default 50 MB).
Any suggestion are appreciated .
Pegasystems Inc.
US
Hi Brahmeswara,
Without looking at the complete ALERT and StackTrace we cannot confirm that the WARNING PEGA0004 alert that you see is related to the specific issue documented under SA-1597 in PDN. Rather, we think the WO has an attachment reference which has a quantity of data (bytes) that exceeds the warn limit/threshold.
Coming to your second question. Our recommendation is to typically avoid fetching un-exposed columns in reporting rules. This is to ensure that that the entire BLOB (pzPVStream) doesn't get loaded from the DB thereby generating the ERROR. However, if such properties cannot be exposed or the reporting rules changed then you may go ahead and change the ALERT threshold. The following is the PDN article which states prconfig environment variable to modify the ALERT thresholds/generate stacktrace. Value should be set to something which is larger than the largest BLOB size in your database table.
Pegasystems Inc.
US
Let me address your questions in reverse order.
Based on your alert message it appears you may have your interactionByteThreshold/warnMB set to 5 MB rather than the default 50 MB.
"Maximum bytes: 5000000 Actual bytes: 5556815"
There is an article that describes the Pega0004 alert and how to modify the interactionByteThreshold. http://pdn.pega.com/understanding-pega0004-alert-quantity-data-received-database-query-exceeds-limit
I would suggest checking that article and verifying whether the following setting has been modified:
<env name="alerts/database/interactionByteThreshold/warnMB" value="50" />
All indications are that alerts you are seeing are for interactions above 5 MB. In which case they would be substantially smaller and less of a concern.
Let me address your questions in reverse order.
Based on your alert message it appears you may have your interactionByteThreshold/warnMB set to 5 MB rather than the default 50 MB.
"Maximum bytes: 5000000 Actual bytes: 5556815"
There is an article that describes the Pega0004 alert and how to modify the interactionByteThreshold. http://pdn.pega.com/understanding-pega0004-alert-quantity-data-received-database-query-exceeds-limit
I would suggest checking that article and verifying whether the following setting has been modified:
<env name="alerts/database/interactionByteThreshold/warnMB" value="50" />
All indications are that alerts you are seeing are for interactions above 5 MB. In which case they would be substantially smaller and less of a concern.
Regarding the Rule-Utility-Function HaveAttachmentSpecificAccess, the issue noted in the article (https://community.pega.com/support/support-articles/seeing-pega0004-when-user-accesses-attachments-list) was to be addressed in Pega 7.1.7, so you shouldn't see that taking place if you are running Pega 7.1.8. Given that your alert setting appears to be artificially low however, you may be getting a false alert in this case.
I would advise checking whether or not the interactionByteThreshold has been reduced to 5 MB. Based on that I would validate whether or not that is triggering the alerts early when in fact you aren't having memory issues. If you correct the setting and still see the alerts for HaveAttachmentSpecificAccess, I would suggest opening a Support Request to have the issue investigated further.
Skandiabanken
SE
Thanks for the response.
>> Plan to have interactionByteThreshold/warnMB set to 50 MB(default) rather than the 5 MB.
>> The same exception(DB Bytes Read) is happeing with ServiceLevelProcessEvent as well .
Thanks for the response.
>> Plan to have interactionByteThreshold/warnMB set to 50 MB(default) rather than the 5 MB.
>> The same exception(DB Bytes Read) is happeing with ServiceLevelProcessEvent as well .
07:00:02,626 [ PegaRULES-Batch-2] ( internal.access.DatabaseImpl) ALERT - 2016-07-03 07:00:02,626 GMT*8*PEGA0004*12213097*5000000*4410a3de40c50d29bc41922d0fb2ae30*NA*NA*B6698FF536A5EB777D777D75BABA4197B*System*b568661c85ea6511186b04942c227553*N*5*B6698FF536A5EB777D777D75BABA4197B*959*PegaRULES-Batch-2*STANDARD*com.pega.pegarules.data.internal.access.DatabaseImpl**System-Queue-ServiceLevel.ProcessEvent*Rule-Obj-Activity:EstablishContext*WORK- WORKLOCK #20130919T002547.105 GMT Step: 2 Circum: 0******pxCommitRowCount=20;pxRDBIOElapsed=.06;pxListWithUnfilteredStreamCount=14;pxRDBIOCount=26;pxTotalReqCPU=0.21;pxRunWhenCount=54;pxRulesExecuted=114;pxListRowWithUnfilteredStreamCount=14;pxOtherCount=31;pxDBInputBytes=12,668,707;pxTotalReqTime=0.58;pxActivityCount=103;pxAlertCount=1;pxOtherFromCacheCount=40;pxRDBWithoutStreamCount=4;pxCommitCount=13;pxOtherBrowseElapsed=0.03;pxDeclarativeRulesInvokedCount=1;pxInteractions=5;pxRuleCount=29;pxRulesUsed=485;pxRuleFromCacheCount=29;pxOtherIOElapsed=0.19;pxCommitElapsed=0.18;pxTrackedPropertyChangesCount=12;pxDBOutputBytes=443,812;pxRDBRowWithoutStreamCount=4;pxOtherIOCount=56;*Work-*pyWorkPage*Work-*pyWorkPage*Obj-Open-By-Handle;RULE-OBJ-ACTIVITY WORK- WORKLOCK #20130919T002547.105 GMT Step: 2 Circum: 0;doActivity Rule-Obj-Activity:WorkLock;Call WorkLock;RULE-OBJ-ACTIVITY ASSIGN- OPENANDLOCKWORK #20150428T062633.368 GMT Step: 6 Circum: 0;5 additional frames in stack;*assignPage=newAssignPage;skipPerformAssignmentCheck=true;activityParamPageProp=pyActivityParameters;checkOptimistic=true;SLAAction=;workHandle="MyApp-MyORg-MyUnit-Work Case-1234 ;activityToExecuteProp=.pyEscalations(Goal).pyEscalationActions;pyQueueClass=System-Queue-ServiceLevel;workPage=pyWorkPage;QueueNumber=0;coverPage=pyWorkCover;currentItemId=SYSTEM-QUEUE-SERVICELEVEL 146724468630000012E3EB5EF827A24D08968141E7C3A440;SuccessIndicator=0;Event=Goal;skipFlowActionPopulate=true;LockString=0 System-Queue-ServiceLevel.ProcessEvent System-Queue-ServiceLevel;*The number of database bytes input for this interaction has exceeded the WARNING level for Requestor B6698FF536A5EB777D777D75BABA4197B, operator System Maximum bytes: 5000000 Actual bytes: 12213097*