PEGA0007 alert: Database operation time exceeds limit

The PEGA0007 alert is triggered when a database operation takes longer to complete than the operation time threshold setting.

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

Example message text

Database operation took more than the threshold of 500 ms: 6530.86 ms SQL: select pzPVStream from pr4_history_rule where pxHistoryForReference = ? and pxObjClass = ? order by 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 can view the alert logs, this setting is important, because the data 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 the note above.

Reason for the alert

Examine the text of the alert message that describes the SQL statement that the system ran. Ask a database administrator to analyze the SQL and determine 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 column.

Have a question? Get answers now.

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