we are planning to upgrade our Customer's Call Manager from 4.1(3) to 6.1(2)and am fortunate enough to have a 'test' system.
I have loaded and run the Data Migration Assistant 6.1(2) on the test system and it fail sValidation with 6 errors similar to this:-
***> DATA PROCESSING TESTS REVEALED AN ISSUE WHICH GENERATED THE FOLLOWING EVENT:
The error number is: [-691]
The error message is: [-691 Missing key in referenced table for referential constraint
The following additional event information is available:
This record was not processed because another record it needs,
(see reference name listed below), is missing. This likely may be due to a previous error
already reported in the log above, or the result of Directory Services Export issues
reported separately, or due to missing Product, Locale, or other add-on definition CSV
files that should exist on the source system but do not.
SUGGESTED ACTION: Resolve all prior reported issues. If none, look at the Suspected Field,
if listed, for an indication of what data reference could not be resolved. Some hints:
- if ...DirGroup related, check for a Directory Export failure
- if ...Locale related, check for a missing Locale Plug-In
Re-execute DMA when all other issues are addressed.
Suspected Field/Item Is [DMABack_Admin.fk_phonebutton_fkphonetemplate]
TABLE NAME IS [PhoneButton ]
label 'Speed Dial'
According to the error this appears to be a missing 'key' in the PhoneTemplate table.
The foreign key being reported is the 'Standard Tandberg Video' phone template, which has 2 lines and 4 speed dials and is a standard CCM template. The 6 errors are 1 for each button, i.e. they all reference the same foreign key in the 'PhoneButton' table and that key is there in the 'PhoneTemplate' table. I can see no foreign keys in the 'PhoneTemplate' table refering back to the 'PhoneButton' tabel, so I am unsure as to where the 'Missing key in referenced table for referential constraint' is? The DMA says these errors must be fixed for th emigrated data to be valid, but anyone know to fix them when the 'key' appears to be in the 2 referenced tables in SQL Enterprise Manager.