PEGA0002 alert: Commit operation time exceeds limit

The PEGA0002 alert is triggered when the elapsed time for a database commit operation exceeds the operation time threshold setting.

Example message text

Database commit took more than threshold of 500 ms: 1075.23 ms

Default prconfig.xml setting

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

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

Reasons for the alert

An activity or some other process might be trying to commit too much data. For example, there might be an activity with 27 deferred save steps, and one commit at the end of the activity that commits all of the data from all 27 saves.

The database might have a problem with its internal index that causes a simple commit could take too long.

Related topics

PEGA0003 alert: Rollback operation time exceeds limit

PEGA0005 alert: Query time exceeds limit

PEGA0042 alert: Packaging of database query has exceeded operation time threshold


100% found this useful

Have a question? Get answers now.

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