Question

MSSQL Primary key violation related errors found @ Wily but not @ PEGA logs.

Hi Team,

The below mentioned PRIMARY KEY VIOLATION errors has been observed to be reported by Wily but the same havent been displayed @ PEGA Logs.

Any clue about this behavior ?

·1) Error Message: Backends|csx1l on qclspega1l.corp.agp.ads\pega1l-55967 (MS SQL Server DB)|SQL|Default: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'pr_sys_locks_PK'. Cannot insert duplicate key in object 'dbo.pr_sys_locks'. The duplicate key value is (ANTM-CS-NCC-WORK-INTERACTION I-85053587).

2)Error Message: Backends|pega_ip on qclspega1l.corp.agp.ads\pega1l-55967 (MS SQL Server DB)|SQL|Default: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'CPMHC_WORK_PART_INSKEY_PK'. Cannot insert duplicate key in object 'dbo.CPMHC_WORK'. The duplicate key value is (ANTM-CS-NCC-WORK-INTERACTION I-85053617).

3)Error Message: Backends|pega_ip on qclspega1l.corp.agp.ads\pega1l-55967 (MS SQL Server DB)|SQL|Default: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'pc_assign_worklist_PART_PK'. Cannot insert duplicate key in object 'dbo.pc_assign_worklist'. The duplicate key value is (ASSIGN-WORKLIST ANTM-CS-NCC-WORK CLCR-121212123393!MCRCLAIMSRESOLUTION).

Correct Answer
May 29, 2019 - 1:12pm

If I can answer for Nick, what likely happened is that when the error occurred, it was logged at the lowest level by the database system.  However, when Pega saw the error, it swallowed it and then executed the alternate operation, which worked.  As our logic is set up to deal with this case and does not consider it an error, no error is logged to the PegaRULES log.

Comments

Keep up to date on this post and subscribe to comments

May 29, 2019 - 11:11am

If it's not being seen in the Pega logs, what is likely happening is when we try an insert and it fails like this, the exception is caught and an update is issued after.

May 29, 2019 - 11:34am
Response to NickLoving_GCS

Hi Nick,

Thanks for the response but the explanation is not clear.

Could you elaborate or rephrase ? Thanks again.

Pega
May 29, 2019 - 1:12pm
Response to PradeepChowdaryP

If I can answer for Nick, what likely happened is that when the error occurred, it was logged at the lowest level by the database system.  However, when Pega saw the error, it swallowed it and then executed the alternate operation, which worked.  As our logic is set up to deal with this case and does not consider it an error, no error is logged to the PegaRULES log.