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
>> 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?
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.
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.