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.

Published April 12, 2017 - Updated April 25, 2017

Have a question? Get answers now.

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