Question

3
Replies
167
Views
PradeepPydi Member since 2017 202 posts
Anthem
Posted: 1 year ago
Last activity: 1 year 2 months ago
Closed
Solved

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).

Data Integration Java and Activities System Administration
Moderation Team has archived post
Share this page LinkedIn