MSSQL Error: Violation of PRIMARY KEY constraint CMN_SEC_ASSGND_OBJ_PERM_PK After Database Upgrade/Restore

Products

• Clarity PPM On Premise

Issue/Introduction

After restoring the MSSQL database backup, various actions are giving a generic error:
 System error . Contact System Administrator.

The APP logs show:

Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'CMN_SEC_ASSGND_OBJ_PERM_PK'. Cannot insert duplicate key in object 'niku.CMN_SEC_ASSGND_OBJ_PERM'. The duplicate key value is (100609427).
SQL error code: 3621

Environment

Release : 15.8

Component : CA PPM PROJECT MANAGEMENT

Cause

 

 

Resolution

In one case study, obtaining the database and restoring it to the Support team's servers did not yield any issues. 

Upon restoring the database, by placing all active process, particularly those that assign rights via direct database update to CMN_SEC_ASSGND_OBJ_PERM, on hold, the issue was not able to be reproduced.