Question
Coforge
AU
Last activity: 27 Jul 2021 4:41 EDT
How to resolve PEGA0005 alert due to pr_sys_locks insert query
We are getting below PEGA0005 alert in our logs. Please let us know how to resolve the below alert
We are getting below PEGA0005 alert in our logs. Please let us know how to resolve the below alert
2021-07-26 01:23:26,422 GMT*8*PEGA0005*936*500*c2a2026849968e51796591c5c97b9fc8*NA*NA*BK1U2UJDPS4DDT0D3FT5CHFI33TF2OTCAA*------*------FW-KM-Work*KM----_0624:01.01.01*07e869344c7728e315f5a0dcbc98efcb*N*1*BK1U2UJDPS4DDT0D3FT5CHFI33TF2OTCAA*9785*PegaRULES-Batch-5*STANDARD*com.pega.pegarules.data.internal.store.DataStorePreparedStatement*NA*Work-Cover-.UpdateOpenCoveredTasks*Rule-Obj-Activity:InitialProfileSetup*WORK- WORKLOCK #20180713T132209.359 GMT Step: 2 Circum: 0*NA*****pxRDBIOElapsed=0.09;pxDBOpExceedingThresholdCount=1;pxInteractions=1;pxRuleCount=19;pxRDBIOCount=1;pxTotalReqCPU=0.04;pxRulesUsed=252;pxRunWhenCount=18;pxRulesExecuted=72;pxOtherCount=167;pxRuleFromCacheCount=19;pxOtherIOElapsed=0.23;pxTrackedPropertyChangesCount=5;pxRDBRowWithoutStreamCount=40;pxDBInputBytes=387,178;pxTotalReqTime=4.18;pxActivityCount=49;pxOtherIOCount=18;pxAlertCount=2;pxOtherFromCacheCount=173;pxRDBWithoutStreamCount=1;*Work-*NA*------FW-KM-Work-Content-ChildContentStage-Published*TempWorkPage*Obj-Open-By-Handle;RULE-OBJ-ACTIVITY WORK- WORKLOCK #20180713T132209.359 GMT Step: 2 Circum: 0;doActivity Rule-Obj-Activity:WorkLock;Java;RULE-OBJ-ACTIVITY WORK-COVER- UPDATEOPENCOVEREDTASKS #20180713T133047.997 GMT Step: 4 Circum: 0;2 additional frames in stack;*workPage=[removed];SuccessIndicator=[removed];workOnly=[removed];workHandle=[removed];*Database update took more than the threshold of 500 ms: 936 ms SQL: insert into KM841_PROD_DATA.pr_sys_locks ( pxCreateDateTime, pxCreateOpName, pxCreateOperator, pxCreateSystemID, pxExpireDateTime, pxLockHandle, pxObjClass, pxOwnerId, pxSystemName, pxSystemNode, pxUpdateDateTime, pxUpdateOpName, pxUpdateOperator, pxUpdateSystemID, pxUserHost, pyLabel, pzInsKey) values (?, ?, ?, ?, ?, ?, 'System-Locks', ?, ?, ?, ?, ?, ?, ?, ?, '', ?)*
***Edited by Moderator: Pooja Gadige to add platform capability tag***
Tata Consultancy Services
US
@DixitGoyal I think, query time taking long time (936ms) than usual(500ms) which is configured in prconfig.xml. You can change that value by creating DSS or you can update in prconfig.xml in following path. it will works.
"alerts/database/operationTimeThreshold"
Coforge
AU
@MALLIKHARJUN Thanks for the solution. But we are trying to figure out a way to reduce the time taken by the query.