Question

Deadlock Queries @ Production Environment.

Hi Team,

Below mentioned Deadlock Queries has been observed @ Production Environment.

Please suggest.

1) SELECT TOP 1000 [pxAssignedOperatorID] ,[pxObjClass] ,[pxRefObjectClass] ,[pxRefObjectInsName] ,[pxRefObjectKey] ,[pxServiceLevelName] ,[pxUrgencyAssign] ,[pxWorkGroup] ,[pyAssignmentStatus] ,[pyFlowType] ,[pyInstructions] ,[pyLabel] ,[pzInsKey] ,[pxApplication] ,[Market] ,[ReceivedDate] ,MemberID ,ProviderID ,DocumentID ,MemberName FROM [pc_assign_workbasket] where pxobjclass='Assign-WorkBasket' and pxRefObjectClass like 'Antm-%' and pxAssignedOperatorID = ? and pyAssignmentStatus like 'Open-Assigned-%' and pxWorkGroup like 'CompassClinical%' Order by ReceivedDate asc

2) SELECT "PC0"."pxUrgencyAssign" AS "pxUrgencyAssign" , "PC0"."pxRefObjectInsName" AS "pxRefObjectInsName" , "PC0"."pyLabel" AS "pyLabel" , "PC0"."pyAssignmentStatus" AS "pyAssignmentStatus" , "PC0"."pyInstructions" AS "pyInstructions" , "PC0"."pyAssignmentStatus" AS "pyAssignmentStatus" , "PC0"."pxDeadlineTime" AS "pxDeadlineTime" , "PC0"."pxAssignedOperatorID" AS "pxAssignedOperatorID" , "PC0"."pxUpdateOperator" AS "pxUpdateOperator" , "PC0"."pxUpdateDateTime" AS "pxUpdateDateTime" , "PC0"."pxGoalTime" AS "pxGoalTime" , "PC0"."pxCreateOpName" AS "pxCreateOpName" , "PC0"."pxCreateDateTime" AS "pxCreateDateTime" , "PC0"."pxTaskLabel" AS "pxTaskLabel" , "PC0"."pxAssignedUserName" AS "pxAssignedUserName" , "PC0"."pzInsKey" AS "pzInsKey" FROM dbo.pc_assign_worklist "PC0" WHERE ( "PC0"."pxAssignedOperatorID" = ? ) AND "PC0"."pxObjClass" = ? ORDER BY 1 DESC, 7 ASC, 13 DESC

3) SELECT "MemberID" AS "MemberID" , "pxCreateDateTime" AS "pxCreateDateTime" , "pxObjClass" AS "pxObjClass" , "pyID" AS "pyID" , "pyDescription" AS "pyDescription" , "pyStatusWork" AS "pyStatusWork" , "WorkbasketName" AS "WorkbasketName" , "MemberLOB" AS "MemberLOB" , "MemberFullName" AS "MemberFullName" , "ProviderName" AS "ProviderName" , "ProviderNumber" AS "ProviderNumber" , "pxCreateOperator" AS "pxCreateOperator" , "DualMemberID" AS "DualMemberID" , "DocumentID" AS "DocumentID" , "FaxWOID" AS "FaxWOID" , "pyResolvedTimestamp" AS "pyResolvedTimestamp" , "pxUpdateDateTime" AS "pxUpdateDateTime" , "pzInsKey" AS "pzInsKey" from dbo.CPMHC_WORK WHERE ( "MemberID" = ? ) AND "pxCreateDateTime" >= ? AND "pxCreateDateTime" <= ? AND ( "pxObjClass" NOT LIKE ? ) AND "pxObjClass" IS NOT NULL ORDER BY "pxCreateDateTime" DESC

4) delete from dbo.pr_idx_MemberBilling_SSNDeductions where pxInsIndexedKey = ? and pxIndexPurpose = ?

5) select pzPVStream from dbo.CPMHC_WORK where pzInsKey = ?

6) select pzPVStream , pxCommitDateTime from dbo.pc_assign_workbasket where pzInsKey = ?

***Edited by Moderator Marissa to update SR Details***

Group Tags

Correct Answer
May 28, 2019 - 9:56am

Issue got fixed after enabling READ_COMMIT_SNAPSHOT DB setting (MSSQL).

Thank you.

Comments

Keep up to date on this post and subscribe to comments

Pega
July 9, 2018 - 8:58pm

Hi Pradeep,

  • Please attach the PegaRULES and PegaRULES-ALERT logs with an approximate time of deadlock.
  • Is there a specific use case where this deadlock occurrence has been observed?
  • Which version of Pega are you using?

August 28, 2018 - 10:08am

We are facing similar deadlock scenario.Did you get update from pega support.. what was the solution provided provided for this issue

August 29, 2018 - 2:21am
Response to KavithaEthirajalu

Hi,

Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.

You may also refer this discussion link as a reference in the new thread.

Vidyaranjan | Community Moderator | Pegasystems Inc.

Mod
May 28, 2019 - 4:57am

Hi @PradeepChowdaryP

On reviewing the SR we see that it was closed because there was no response from you. Please let us know if you found a solution.

Thank you,

Lochana | Community Moderator | Pegasystems Inc.

May 28, 2019 - 9:56am

Issue got fixed after enabling READ_COMMIT_SNAPSHOT DB setting (MSSQL).

Thank you.

Mod
May 28, 2019 - 10:23am
Response to PradeepChowdaryP

Thank you for updating this post with the resolution!

Lochana | Community Moderator | Pegasystems Inc.