5.5 The PEGA0033 alert is generated if your Process Commander system sends to the PegaRULES database (or to another SQL database) a SQL query with length in bytes greater than a specified threshold. BYTES OR CHARS?
Such large SQL queries expand the size of database cache memory and increase memory and CPU resource costs. Here is an example of a long query:
Database query length exceeded the defined threshold value of 2,500: 5,151 SQL: SELECT pzInsKey as "pxInsHandle", pyClassName AS "pyClassName" , pyFlowType AS "pyFlowType" , pyLabel AS "pyLabel" , pyRuleSet AS "pyRuleSet" , pyRuleSetVersion AS "pyRuleSetVersion" , pyCategory AS "pyCategory" , pyCanStartInteractively AS "pyCanStartInteractively" , pyCanCreateWorkObject AS "pyCanCreateWorkObject" , pyStreamName AS "pyStreamName" , pyMethodStatus AS …
By default, the alert is disabled. When enabled, it has a threshold of
2,500 bytes. You can modify the setting in the prconfig.xml
file as follows:
prconfig.xml
file and update this alerts
section:<env
name="alerts/database/querylength/enabled"
value="false" />
<env name="alerts/database/querylength/threshold"
value="2500" />
For an example, see Pega Developer Network article PRKB-25676 Understanding the PEGA0033 alert.
alert log, prconfig.xml file | |
Understanding
alerts
Working with the PegaRULES database |