Nov 202016
 

Warning! If you have added custom indexes to the VMware vCenter database, you will need to remove them completely before you can complete a vCenter 6.5 upgrade. If they are still present in the database, the upgrade wizard throws an error.

vcenter65_01

The error file tells you specifically which indexes it does not like. The error file is found at:

C:\Users\(youraccount)\AppData\Local\Temp\vcsUpgrade\vcdb_req.err

You’ll find the error message towards the bottom of the document. My specific item was:

1 [42000](50000) [Microsoft][SQL Server Native Client 11.0][SQL Server]ERROR ! Extra indexes: VPX_EVENT.HFX_VPX_EVENT_Cover01; VPX_STAT_COUNTER.IX_VPX_STAT_COUNTER_STAT; VPX_TASK.HFX_VPX_TASK_Cover01;

Drop the indexes and retry the upgrade and it should get past this point without a problem.

Such is the risk we all take with modifying the databases underneath third party software…

  One Response to “Custom indexes on VMware vCenter database breaks 6.5 upgrade”

  1. […] David Klee shows the risk of creating custom indexes on third-party software: […]

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close