Problem:
When upgrading from CCM 4.1(3) to Cisco UCM 7.x we got an error using the Data Migration Assistant (DMA 7.1(3)). The DMA starts and at the same time it stopps the "Informix IDS - ccm" service. After configuring the prerequisits the DMA checks the "Informix IDS - ccm" service and ended with the error "Error connecting to Database". We were not able to start the "Informix IDS - ccm" service manually.
Resolution:
We fixed the problem by stopping the "Informix Server Discovery process for SNMP" after the publisher was restarted. If this service is stopped before starting the DMA the "Informix IDS - ccm" service keeps running and the migration is running succesfull.
Problem:
When running DMA for migration from CCM 4.2(3) to CUCM 7.1(3) the result
is; "Export Successful.Validation Successful with Warnings"
Resolution:
The information from the DMA warnings were collected and following corrective actions are recommended:
- Warning: UserID:rdavé: is invalid - User profile not found in LDAP search
Condition: The user profile for the user does not exist
Solution: you need to verify that the user is a valid CUCM user. For that you need to access the user
through the CUCM Admin page and associate a device to the user.
Then disassociate the same device. This procedure will create the required profile for the user
- Warning: Numplan (NULL) for User pmorton is invalid. Ignoring the user
Condition: Primary Extension for this user is invalid. It does not exist in the database
Solution: You need to ensure that the user is associated with a valid primary extension/numplan
Regarding these warnings:
Table: VoiceMessagingProfile
Row: 2 SQL error: -746(36071)
Error executing "update VoiceMessagingProfile set Name='VMP - Conted
Queue' where pkid='87904580-168b-452c-9a42-32198ca12896'":
[Informix][Informix ODBC Driver][Informix]Unspecified System Error = -746.
sqlerrm(36071)
pkid 87904580-168b-452c-9a42-32198ca12896
NOT MODIFIABLE
Name VMP - Conted Queue
Description VMP - Conted Queue
fkVoiceMessagingPilot
VoiceMailBoxMask 5000
IsDefault false NOT MODIFIABLE
resetToggle false
tkReset 2
VersionStamp
0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Row: 7 SQL error: -746(36071)
Error executing "update VoiceMessagingProfile set Name='Health Services
Transfer to 6326' where pkid='7ec0d62d-2d3d-486f-9f3a-afe51e9e39b9'":
[Informix][Informix ODBC Driver][Informix]Unspecified System Error = -746.
sqlerrm(36071)
pkid 7ec0d62d-2d3d-486f-9f3a-afe51e9e39b9 NOT
MODIFIABLE
Name Health Services Transfer to 6326
Description Health Services Transfer VM
calls to 6326
fkVoiceMessagingPilot
VoiceMailBoxMask 6326
IsDefault false NOT MODIFIABLE
resetToggle false
tkReset 2
VersionStamp
0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Row: 10 SQL error: -746(36071)
Error executing "update VoiceMessagingProfile set Name='Communications
News Room' where pkid='e63f60d4-fe09-4d71-9852-c40b2d995cfe'":
[Informix][Informix ODBC Driver][Informix]Unspecified System Error = -746.
sqlerrm(36071)
pkid e63f60d4-fe09-4d71-9852-c40b2d995cfe NOT
MODIFIABLE
Name Communications News Room
Description News RoomTransfer VM calls to
6991
fkVoiceMessagingPilot
VoiceMailBoxMask 6991
IsDefault false NOT MODIFIABLE
resetToggle false
tkReset 2
VersionStamp
0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Solution: You need to make sure that you have the names and description populated without any special characters
and less than 24 characters in all.
Also, You need to delete if there is any unassigned DNs in your system.
DMA Validation Fails
While trying to perform DMA, you got this error "Export - Successful. Validation - Failed."
Resolution
After checking DMA logs found the following error:
=========
***> DATA PROCESSING TESTS REVEALED AN ISSUE WHICH GENERATED THE FOLLOWING EVENT:
The error number is: [-391] The error message is: [-391 Cannot insert a null into column column-name.]
The following additional event information is available:
This record was not processed because it is missing a required value.
This could also be caused by specifying the value NULL in a required field.
Suspected Field/Item Is [enduser.lastname]
=========
This issue was occurred because there are some users in your system without last name/ sure name and this field is
required so it shouldn't be NULL, after adding sure name, the problem is resolved.
Related Information
