Problem Description

Following Error/warning encountered while analyzing the .Net or UA Analysis

SQL Error: Violation of PRIMARY KEY constraint 'PK_KeyPar'. Cannot insert duplicate key in object 'dbo.KeyPar'.
SQL Error: The CREATE UNIQUE INDEX has been interrupted because a duplicate key was found for object 'dbo. AccLinkSymb_00000005E93E #' and index 'IDX_TmpAccLinkS' . Duplicate key value:
SQL Error: The statement has been terminated.

or

SQL Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK_ACCIDACC'. Cannot insert duplicate key in object 'dbo.Acc'. The duplicate key value is (729782). (Severity 1, Msg No 2627).

Applicable in CAST Version
Release
Yes/No
8.3.x(error)
8.2.x(error)
8.1.x(error)
8.0.x(error)
7.3.x(error)
7.2.x(error)
7.0.x(tick)
RDBMS
Yes/No
Oracle Server(error)
Microsoft SQL Server(tick)
CSS2(error)
CSS1(error)
Action Plan

From 7.0.8 up to 7.0.12 versions, under SQL Server, the links escalation process was not updating the Parms table, leading to massive potential duplicate between objects and links, and to frequent duplicate error between two objects or two links.  

The workaround is to: 

  1. Totally disable links escalation from any KB stored under SQL Server [ for this: open AnaMan and set the Escalate Links to False under Analysis options for every project]
  2. Check & repair the corruption SQL Queries - CAST Knowledge Base - Corruptions
  3. Rerun analysis

This issue is particularly raised on SQL Server bases and on version 7.0.9 & 7.0.10 and this has been fixed in CAST 7.0.13

Notes

 

Related Pages