vCenter 6.5 Upgrade Error: VMware Migration Assistant Failed Due To An Extra Indexes Of The vCenter Database

This issue appeared in the VMware Migration Assistant and it was failing the pre-checks of the vCenter due to extra indexes of The vCenter Database. I hope you already aware of the vCenter 6.5 Windows to VMware vCenter Appliance Migration process and you can read the Windows to vCenter 6.7 Migration process in my previous post. There is no difference in the vCenter 6.5 VCSA migration process when compared to the vCenter server 6.7 Migration which I explained in that post.

Also, If you have a separate Single Sign-On server and you are planning to migrate them to a separate PSC and vCenter you can follow this article which I published earlier.

This error message showed up as below in the screen capture of my Migration Assistant.

Migration assistant log file was showing some error entries and below error appeared in each error section

So this was due to the extra indexes of The vCenter database tables and those indexes should be removed before proceed with the Migration Assistant, this happens when the vCenter server migrated from older versions to newer versions, in my case this vCenter server was upgraded from vCenter server 4.1 to 5.5 and 6.0 , this error appeared when we were upgrading from vCenter server 6.0 to 6.5 Appliance.

This type of similar entries could be seeing in the “vcdb_req.err” log

Remove The Indexes From The Database

So we took a backup of the database as the safety measure and executed below database query to remove this index

USE [<vCenter_database_name>]
GO

/****** Object:  Index [VPX_EVENT_ALLColumns]    Script Date: 07/27/2018 09:17:26 ******/
IF  EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[VPX_EVENT]') AND name = N'VPX_EVENT_ALLColumns')
DROP INDEX [VPX_EVENT_ALLColumns] ON [dbo].[VPX_EVENT] WITH ( ONLINE = OFF )
GO

After removing the extra indexes of the database make sure to check the vCenter Server functionality and run the VMware Migration Assistant, this would fix the problem and I can confirm this worked all the time in our upgrades.

If you found this post as useful please rate the post and share it!