Question

1
Replies
19
Views
Harsha45 Member since 2018 8 posts
Tata Consultancy Services
Posted: October 7, 2020
Last activity: October 8, 2020

High volume of Pega Alert 0005 on pr_data table

We are getting Pega alert 0005 on pr_data  table on high volume.

Sample alert:-

(1) Database operation took more than the threshold of 500 ms: 26,763 ms         SQL: SELECT "PZPVSTREAM" AS "pzPVStream", "PZINSKEY" as "pxInsHandle"  from PH_WBNLCHPS_DATA_OWNER.pr_data  WHERE ( "PZINSKEY" LIKE ? ) AND (  "PXOBJCLASS" = ?  )    inserts: <%ING-WORK SRVC00033-210220%> <PegaCommBank-Corr-Swift>

 

(2) Database operation took more than the threshold of 500 ms: 520 ms     SQL: SELECT "PC0"."UTI" AS "UTI" , "PC0"."EXCEPTIONREF" AS "EXCEPTIONREF" , "PC0"."LINKDATE" AS "LINKDATE" , "PC0"."NOTE" AS "NOTE" , "PC0"."OPERATORID" AS "OPERATORID" , "PC0"."SOURCESYSTEM" AS "SOURCESYSTEM" FROM PH_WBNLCHPS_DATA_OWNER.Research_Links "PC0" INNER JOIN PH_WBNLCHPS_DATA_OWNER.pr_data "Test" ON ( ( "PC0"."UTI" = "Test"."PYLABEL" )  AND "Test"."PXOBJCLASS" = ? )          inserts: <Data-Transaction_Test> *

 

(3) Database operation took more than the threshold of 500 ms: 404,580 ms            SQL: SELECT "PZPVSTREAM" AS "pzPVStream" FROM  PH_WBNLCHPS_DATA_OWNER.pr_data   WHERE    ( "SICORRATTACHSTATUS" = ? )   AND   ( "PXOBJCLASS" LIKE ? )   inserts: <Not Yet Sent> <PegaCommBank-Corr-%> *

Please suggest some solution to  resolve this alert.

Pega Platform 7.2.2 System Administration System Administrator
Share this page LinkedIn