How to detect lengthy PegaRULES database operations
(PEGA0002, PEGA0003, PEGA0005 alerts)

Benefits

Process Commander adds a line to the alert log when the PegaRULES database takes an unusually long time to respond to a request from the server. The message has one of these formats, with additional details about the date, time, and requestor:

PEGA0002 Database commit operation has exceeded a threshold setting.
PEGA0003 Database rollback operation has exceeded a threshold setting.
PEGA0005 Database query operation has exceeded a threshold setting.

For your requestor session, a count of database requests that take longer than a fixed threshold value appears in the Requestor Summary section of the Details display of the Performance tool.

By default, the threshold value is set to 500 milliseconds. Through a prconfig.xml file setting, you can choose a larger or smaller threshold, or disable this feature.

In a development environment, such monitoring allows you to identify and isolate those database requests that are complex or place heavy demands on the database. Such requests may affect overall system response, and may indicate areas of the database or of the application that need attention.

A PEGA0005 alert may arise from various sources, such as the list view reports, summary view reports, and the RDB-Browse method operating on an external database.

Changing the threshold value

1. Edit the prconfig.xml file to set a cutoff value for the operationTimeThreshold element in milliseconds. For example, to set the value to 850 milliseconds, add these elements:

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

The optional suppressInserts element causes values of properties in SQL statements to be replaced by a single ? character in the alert log. When omitted, the default value is true. If you explicitly set this value to false, the PEGA0005 alert may contain the value of passwords, account numbers, or other sensitive property values.

2. Stop and restart the application server to make this change effective.

3. Monitor the alert log for messages identified by the PEGA000X tags listed above. The alert log identifies the elapsed time, the original SQL statement, and the converted SQL statement.

If the operationTimeThreshold element is not present in the prconfig.xml file, the default value is 500 milliseconds. To disable this feature completely, set a large value such as 20,000 milliseconds.

PDN Articles

For additional examples and explanation of these facilities, consult these Pega Developer Network articles:

• PRKB-25340 Understanding the PEGA0002 Alert
• PRKB-25341 Understanding the PEGA0003 Alert
• PRKB-25342 Understanding the PEGA0005 Alert
• PRKB-23116 How to detect and remedy the performance impact of Obj-List methods and List View reports.

For advanced suggestions on avoiding resource-intensive operations with the PegaRULES database, see Writing SQL, a document available on the Pega Developer Network.

	Alert log, PegaRULES database, Storage Stream
	Working with the PegaRULES database Understanding alerts

SysAdmin category