"Source vCenter Server schema validation found an issue'' while Upgrading/Migrating VC from 6.0 to 6.5

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Upgrading/Migrating vCenter Server from 6.0 to 6.5 fails.
• You see the error:

Error: Source vcenter server schema validation found an issue
Resolution:Read the vcdb_req_err log file and address the issues found

• In the migration-assistant.log file, you see entries similar to:

YYYY-MM-DD HH:MM:SS| migration-assistant-4944578| I: ParseErrorsWarningsFromPreUpgradeOutput: No mismatch to process.
YYYY-MM-DD HH:MM:SS| migration-assistant-4944578| I: ParseErrorsWarningsFromPreUpgradeOutput: Parsed 1 error messages.
YYYY-MM-DD HH:MM:SS| migration-assistant-4944578| I: ParseErrorsWarningsFromPreUpgradeOutput: Error messages: Error: Source vCenter Server schema validation found an issue.

Resolution: Read the vcdb_req.err log file and address the issues found.
 

YYYY-MM-DD HH:MM:SS| migration-assistant-4944578| I: ParseErrorsWarningsFromPreUpgradeOutput: Parsed 1 warning messages.
YYYY-MM-DD HH:MM:SS| migration-assistant-4944578| I: ParseErrorsWarningsFromPreUpgradeOutput: Warning messages: Warning: This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server.

• In the vminst.log file, you see entries similar to:

YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ParsePreUpgradeOutput: Processing pre-upgrade for component [com.vmware.eam]
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ParsePreUpgradeOutput: Export disk req: [0 MB], Import disk req: [0 MB].
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ParsePreUpgradeOutput: Processing pre-upgrade for component [upgrade_framework]
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ParsePreUpgradeOutput: Export disk req: [0 MB], Import disk req: [0 MB].
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ParsePreUpgradeOutput: IC host: 127.0.0.1.
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ParsePreUpgradeOutput: IC port: 7444.
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ParsePreUpgradeOutput: IC URL: /sso-adminserver/sdk/vsphere.local.
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ProcessInstallArguments: processing installArguments for upgrade_framework
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ProcessInstallArguments: vmdir.ldu-guid = 25d5b5a0-f963-11e6-a7ce-e4115bde7480
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: ProcessInstallArguments: vmdir.site-guid = 24a720b0-f963-11e6-a598-e4115bde7480
YYYY-MM-DD HH:MM:SS| vcsInstUtil-5178943| I: PitCA_MessageBox: Displaying message: "Error: Source vCenter Server schema validation found an issue.
Resolution: Read the vcdb_req.err log file and address the issues found.

• In the vcdb_req.err file, you see entries similar to:

1 [42000](50000) [Microsoft][SQL Server Native Client 10.0][SQL Server]ERROR ! Extra indexes: VPX_STAT_COUNTER.VPX_STAT_COUNTER_M1;

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server 6.0.x
VMware vCenter Server 6.5.x

Cause

This issue occurs due to an extra index VPX_STAT_COUNTER_M1 being present under VPX_STAT_COUNTER table.

Resolution

Disclaimer:

• Take a complete vCenter database backup prior to proceeding
• Stop any third party services like backup application

To resolve this issue:

1. Run this command to drop the index VPX_STAT_COUNTER_M1 under VPX_STAT_COUNTER table.

DROP INDEX VPX_STAT_COUNTER_M1 ON VPX_STAT_COUNTER ;

2. Restart the upgrade/migration.

Note: general structure: DROP INDEX <ExtraIndexName> ON <table> ;