PEGA0006 alert: Update operation time exceeds limit

The PEGA0006 alert is triggered when the database update operation time exceeds the threshold.

Update: Beginning with PRPC 5.4, this alert no longer occurs. In PRPC 5.4 and later versions, the condition described here is reported as PEGA0005.

Example message text

Database update took more than threshold of 500 ms: 5358.43 ms SQL: update pr_sys_context set pxContextExpires = ? , pxCreateDateTime = ? , pxInsName = ? , pxLabel = ? , pxObjClass = ? , pxOperator = ? , pxRequestorId = ? , pxUpdateDateTime = ? , pzPVStream = ? where pzInsKey = ?

The question marks in this text example are inserted by the suppressInserts setting, which prevents possibly sensitive property values from being output to the log files. Depending on who is viewing the data, this setting might be extremely important, because some of the data being sent might include system or database passwords (if they are not encrypted).

Default prconfig.xml settings

<env name="alerts/database/operationTimeThreshold" value="500" />

The default threshold is 500 milliseconds (1/2 second).

<env name="alerts/database/operationTimeThreshold/suppressInserts" value="true" />

Toggles the trigger for suppressing insert operations on ("true") or off ("false"). See note above.

If these settings are not included in the prconfig.xml file or Dynamic System Settings, the default behavior is as shown above.

Reason for the alert

Examine the text of the alert message that describes the SQL statement the system was trying to run. Ask your database administrator to analyze the SQL to see whether there are problems with the information that is being requested from the database (for example, is the system trying to query information from the BLOB).

Have a question? Get answers now.

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