EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB305022: New behavior in MicroStrategy 10.3: Enterprise Manager data loads always clean fact tables before migration


Community Admin

• Strategy


New behavior in MicroStrategy 10.3: Enterprise Manager data loads always clean fact tables before migration

In Strategy Enterprise Manager versions 10.2 and prior, Primary Key Violation errors can be common when loading statistics data into the fact tables.  Some examples of such errors:
 
 


[Strategy][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Violation of PRIMARY KEY constraint 'IS_REP_FACT_PK'. Cannot insert duplicate key in object 'dbo.IS_REP_FACT'
 
[Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-00001: unique constraint (MSTRLOG.IS_DOC_FACT_PK) violated ORA-06512: "MSTRLOG.SP_IS_DOC_FACT"

 
 
In order to reduce the possibility of these errors occurring, beginning in Strategy 10.3 the normal Enterprise Manager data load process runs a stored procedure that cleans the IS_REP_FACT and IS_DOC_FACT tables of any data that belongs to the time window that the fact migration will take place for, later in the data load.  Prior to version 10.2 this stored procedure would only be run when performing a custom time window data load.


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017