Cisco UCM (CUCM) Cluster Upgrade Fails from 10.5.1 to 11.0.1 with "DBUtil::BlockCopyTable *ERROR* Violation of the REFERENTIAL" Message

Everything starts at a rainy evening.
All plans has been completed before starting CUCM Cluster Upgrade from 10.5.1 to 11.0.1, but it seems one is missing.

If your CUCM Cluster is integrated with LDAP and your AD contains non-English characters (Like ş,Ş,ç,Ç,İ,ü,Ü,ğ,Ğ,ö,Ö exc.), you will probably face same issue.

After uploading "UCSInstall_UCOS_11.0.1.21900-11.sgn.iso" upgrade file to CUCM Pub server via SFTP or DVD, you will click on "Next" button while choosing "Switch Version after Upgrade" or not.

It will take approximately one hour to get first "DBUtil::BlockCopyTable *ERROR*   Violation of the REFERENTIAL constraint" message on OS Administration GUI of CUCM Publisher server.

This means you do not need to keep on waiting to finish Cluster upgrade, because it is impossible.

Other Error logs are kindly below;

- DBUtil::DoSQLCommand ### *ERROR* ###:  SQL Exception detected while Enabling Target Indexes
- DBUtil::BlockCopyTable ### *ERROR* ###:  SQL Exception Detected:   ErrorCode=-212
- DBUtil::BlockCopyTable *ERROR*   (diagnosis):  Unexplained SQL Exception processing table enduser
- DBUtil::BlockCopyTable ### *ERROR* ###:  (diagnosis):  Bulk Data Migration for table callerfilterlist

Firstly be sure that you already uploaded correct version of CUCM Locale Installer to all nodes.
If this issue occurs in spite of uploading Locale Installer, this is a bug anymore.

CSCux51818 - Upgrade or sync fails with certain Unicode capital letters
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux51818/?reffering_site=dumpcr

Symptom:
Cisco UCM upgrade from 10.x to 11.0(1) or later fails due to database errors. Message similar to the following appears in logs:
SQL Error (-271): Could not insert new row into the table.
An illegal character has been found in the statement.

May also be seen during LDAP sync causing some users not to be inserted into the UCM database.

Conditions:
Certain uppercase characters in Unicode may cause the error if used in fields that are being indexed for localized sort order. The following data from the EndUser table is impacted:

FirstName
LastName
Userid
Department
Mailid

In addition, the Description field in the Device table may also trigger the error.

Only a one character that triggers the error has been found to date (capital i with dot above). There may be other characters although testing with similar characters in the Unicode range where the error happens are able to be inserted.

Workaround:
Convert the uppercase i with dot above to lowercase or another equivalent character in the database or directory.

There is no fixed release for this bug yet on 26th March 2016.

Thats why, please be sure about your AD entries before starting CUCM Cluster Upgrade from 10.5.1 to 11.0.1.

Best Regards,
Mesut

PS : a group of suicide bombers attacked Brussel, Belgium last week on 22th March 2016. We are together with Brussel. As Atatürk said " Peace at Homeland, Peace in the World."