Use the following information to resolve common CommCell migration issues.
Merge operation fails because of barcode collisions
Error
The merge operation fails with an error similar to the following:
[DBErr] Message: BarCode Collision on [n] Media. Please change the following barcode on either Destination or Source CommCell first.
Cause
The source CommCell and destination CommCell contain tapes with the same barcode.
Resolution
Change the barcode of the tape in either the source CommCell or the destination CommCell, and then run the merge operation again.
Export operation fails because of a VM-centric indexing pseudoclient
Error
The export operation fails with an error similar to the following in the CCMManager.log file:
INFO: [Violation of PRIMARY KEY constraint 'PK__#subclie__A6932D4CC00E1A8B'. Cannot insert duplicate key in object 'dbo.#subclientlist'. The duplicate key value is (208, 76).]
CVSimpleDB::SQLINFO() - INFO: [The statement has been terminated.]
Cause
A VM-centric indexing pseudoclient was selected during the export operation.
Resolution
Select the virtual machine that was backed up by the pseudoclient instead of selecting the pseudoclient itself.
Merge operation fails because of unsupported password versions
Error
The merge operation fails and logs an error similar to the following in the CCMManager.log file:
ERROR: CommCell Migration Import failed - Found users with unsupported password version.
Found 1 user(s) with unsupported password version that must be resolved before migration can proceed.
Cause
By default, CommCell migration doesn't migrate users whose passwords use unsupported legacy password versions (earlier than V7).
Resolution
If you want to migrate users with unsupported password versions:
-
Configure the CCM_RESET_INVALID_PWD additional setting on the destination CommServe.
Setting Value CCM_RESET_INVALID_PWD1For more information on creating an additional setting, see For instructions on adding the additional setting, see Adding a CommCell Setting.
-
Restart the CommCell migration.
-
After the migration completes, have the affected users reset their passwords before they sign in.
Important
Enabling the CCM_RESET_INVALID_PWD additional setting resets the passwords for users with unsupported password versions. Those users must create new passwords before they can sign in after the migration.
The software blocks migration of unsupported password versions by default to maintain security and compatibility with current password standards. Enable this setting only when you must migrate legacy users.