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.

Support Article

Query Poor Performance

SA-36424

Summary



REST Service for Pega Mobile offline functionality is executing a Report Definition rule 'PZGETFIELDVALUES' and it takes considerable time to execute.

Database operation took more than the threshold of 250 ms: 900,182 ms SQL: SELECT DISTINCT "PC0"."PYFIELDNAME" AS "pyFieldName" , "PC0"."PYFIELDVALUE" AS "pyFieldValue" , "PC0"."PYCLASSNAME" AS "pyClassName" , TO_CHAR("PC0"."PYLOCALIZEDVALUE") AS "pyLocalizedValue" , "PC0"."PZINSKEY" AS "pzInsKey" , "PC0"."PXINSNAME" AS "pxInsName" FROM PEGARULES721.pr4_fieldvalue "PC0" WHERE ( UPPER("PC0"."PXINSNAME") IN (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) AND UPPER("PC0"."PYRULESET") IN (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? )


Error Messages



Not Applicable


Steps to Reproduce



Check the Pega alert log file for the Pega0005.


Root Cause



A defect in Pegasystems’ code or rules. Reason for the delay is the UPPER() function in the Pega generated query.

Resolution



Apply HFix-33000.

Suggest Edit

Published April 25, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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