-
Title
Data Consistency failed in History Database with Error : " GUID in primary key with invalid format " -
Description
When running Data Consistency Check via designer on the History Database, the check returned the error similar to -:
Error 1:
Check uniqueness as defined in QBMUniqueGroup
--------------------------------------------------------------------------------
SourceColumn ColumnName AccountDisabled
SourceColumn ColumnName AccountExpires
SourceColumn ColumnName DateHead
SourceColumn ColumnName DisplayPersonHead
SourceColumn ColumnName ReasonHead
SourceColumn ColumnName UID_Org
SourceColumn ColumnName UID_Person
SourceColumn ColumnName UID_PersonHead
SourceColumn ColumnName XDateUpdated
SourceColumn ColumnName XObjectKey
SourceColumn ColumnName XUserInserted
SourceColumn ColumnName XUserUpdatedError 2:
GUID in primary key with invalid format
--------------------------------------------------------------------------------
SourceColumn ADS-BF19FD88293E4905ACCA012BC01A8CDD
SourceColumn SAP-41230CECD127433883DA9D76B03348F7
SourceColumn TSB-B18DCD5BE6EC41E19553D2840D58DC35
SourceColumn ADS-80343A707A34407C8F9FCA1A0D7EB44A
SourceColumn TSB-22FBD877986741C2919074B46AED181D
SourceColumn EX0-323A50B112754E9E8EB32BF3C2950A64
SourceColumn ATT-8D143B42F25A4F0D88DBAD22D89C9991
SourceColumn ATT-A455F0D47BA04BB48BD4BC25DC76C620
SourceColumn ATT-47D56CF784A3471EA0872138061639A3
SourceColumn ATT-2D82E29155A4455EB99A003D77CDF5C2
SourceColumn ATT-4F4186E1BCD04D8CA37031B35A382E32
SourceColumn ATT-79DFB6DA61B8442B9FE370C735CEFA12
SourceColumn ATT-CBD7C9A6246548AABDC0FA72636FDD48
SourceColumn EX0-F0C6FF2D91F5451985F2E7E0113A8C68
SourceColumn QER-EFE4D8E2A06C424987CD7CBC85759C88
SourceColumn QER-8F03B89FA2F7451597EAAED8E9B9057B
SourceColumn RMB-1F3950BD34B14BF2BBC35F5A839AB088
SourceColumn ATT-A6EA4B39D35343FCAF8A4D51D7E47AB6
SourceColumn QER-41CE7C5089884FA7A7E08E83D6FDEEF9
SourceColumn ATT-7CFE958464A84365AADF2B4442B5A960
SourceColumn ATT-BB82DEFDB40746BAB80CE313EC32E -
Cause
In v7.1.1, "SouceColumn" was defined as a default in UniqueGroup table which requires unique check.
One of the test Data Consistency Check carries out is to check if the UID are in the correct format.
In the event that the UID is found to be Module Dependent UIDs, the check routine will also determine if the module is installed in the database.
An example in this case -:
ADS- BF19FD88293E4905ACCA012BC01A8CDD, contains the UID prefix, "ADS" . This is an UID prefix for the ADS module.
Data Consistency Check will then check to determine if the module "ADS" is installed in this database.
However, this module cannot be installed in History Database. Hence it is not that the data is inconsistent. but the test carried out was wrong for the History Database.
-
Resolution
Development had informed that in v7.1.1 "SouceColumn" was defined as a default in UniqueGroup table. However this table object is found to be not required and is removed after v7.1.4
In addition, Development has also confirmed that having " GUID in primary key with invalid format " when the check is carried out on the History database is a known issue and has already been resolved in Defect ID #28903. However the fix is only applied to v8.0 and v8.1. The fix is not available in earlier versions.
WORKAROUND:
Ignore " GUID in primary key with invalid format " for "SourceColumn" with Module dependent prefixes in History Database. Development has indicated that the check implemented was wrong but Data is consistent.