Skip to main content
This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

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

The PEGA0042 alert is triggered when the packaging time for a single database query exceeds the threshold setting. Packaging time is defined as the time elapsed from the execution of a query until the last row of the result is returned to the Pega 7 Platform engine. This alert identifies the exceeded threshold, the query string, and the elapsed time for packaging of the query.

Example message text

Packaging of the database query took more than threshold of 500ms: 578ms SQL: select * from tablename

Default prconfig.xml settings

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

The operation time threshold setting is a positive integer value in milliseconds, and sets the alert threshold time for any database operation. If your prconfig.xml file does not contain a value for this setting, the system uses 500 milliseconds, one-half a second.

In addition to the PEGA0042 alert, the operation time threshold setting also applies to three other alerts:

  • PEGA0002 – Commit operation time exceeds limit
  • PEGA0003 – Rollback operation time exceeds limit
  • PEGA0005 – Query time exceeds limit

<env name="alerts/database/packagingTime/warnMs" value="500" />

The warnMs value is a positive integer value in milliseconds, and sets the threshold time for packaging a single query, as defined above.

This setting affects only the PEGA0042 alert, and overrides the operationTimeThreshold setting.

Reasons for the alert

Because of the broad scope of this alert, many different factors could cause it to occur. Examine the query string, and determine which report or other rule caused the alert.

This alert encompasses the total time a query takes, which includes the elapsed time within a query that falls between the boundaries of the other alerts.

Related Topics

PEGA0002 alert: Commit operation time exceeds limit

PEGA0003 alert: Rollback operation time exceeds limit

PEGA0005 alert: Query time exceeds limit

Suggest Edit
Did you find this content helpful?

25% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us