LinkedIn
Copied!

PEGA0003 alert: Rollback operation time exceeds limit

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

Example message text

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

Default prconfig.xml settings

<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 producing too many database operations in a transaction. For example, if an activity contains more than 50 steps, each of which contains an Obj-Save or Obj-Delete method, ending with a Commit method, and a step near the end fails, the earlier operations must be rolled back to ensure database integrity. If that rollback operation requires more than 500 milliseconds to complete, the PEGA0003 alert occurs.

Related topics

PEGA0002 alert: Commit operation time exceeds limit

PEGA0005 alert: Query time exceeds limit

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

Have a question? Get answers now.

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