Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

PEGA0039 alert: BLOB size read from the database exceeded threshold

Updated on January 21, 2022

The PEGA0039 alert occurs when a database query retrieves a BLOB column (pzPVStream property value, also called the Storage Stream) that is larger (in bytes) than the threshold value. The alert provides a warning that memory performance of your system might be affected when the Pega 7 Platform expands the BLOB onto a clipboard page.

In contrast to the PEGA0039 alert, the PEGA0004 alert indicates the size of the entire result set of a query (that might or might not include BLOBs) if the individual row is greater than a threshold.

Example message text

The alert identifies the pzInsKey that was read, and the size in bytes of the BLOB:

Read blob from database with compressed size 26196754 expanded size 53472969. pzInsKey: RULE-FILE-BINARY WEBWB OPENAUTHORING!CAB #20100304T152007.144 GMT

Default prconfig.xml settings

<env name = “alerts/database/blobsizeread/enabled" value="true" />

The enabled value is Boolean. To turn off the alert, set the value to "false",

<env name = “alerts/database/blobsizeread/threshold" value="3" />

The threshold value is a positive integer in megabytes (the default is 3). This value is checked against the compressed size of the BLOB being read.

Stop and restart the server after changing these settings.

Reason for the alert

Examine the record being read (identified by the pzInsKey value and determine whether the entire BLOB is needed. Usually, you can divide the data into additional logical segments (as required by your application).

Tags

Pega Platform 7.1.1 - 8.7 Pega Platform 7.1.1 - 8.7 System Architect System Administration

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us