KB418780: ‘Violation of PRIMARY KEY constraint ‘XXXXXX’. Cannot insert duplicate key in object’ error occurs when trying to create a new attribute in MicroStrategy Developer 9.4.x-10.x

Salesforce Solutions Architect • Strategy

When attempting to copy an existing attribute or create a new one in MicroStrategy Developer 9.4.x-10.x, the following error occurs

SYMPTOM:
When attempting to copy an existing attribute or create a new one in Strategy Developer 9.4.x-10.x, the following error occurs:


Database error <> Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect Violation of PRIMARY KEY constraint 'XXXXXX'. Cannot insert duplicate key in object 'XXXXX'. The statement has been terminated.

CAUSE:
This error is caused by a logical metadata inconsistency. In order to track down the cause of the inconsistency, customers encountering this issue should make note of Schema-related changes, Object Migrations, or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information.
ACTION:
Run ScanMD against the metadata to correct this issue. Refer to the following Strategy Knowledge Base technical note to obtain ScanMD and instructions for its use:
KB35809: Using ScanMD to fix known logical metadata inconsistencies in the MicroStrategy Product Suite 9.4.x - 10.2 Hotfix1
This article has been recorded as

KB418780

Comment

0 comments

Details

Knowledge Article

Published:

April 7, 2017

Last Updated:

November 13, 2018