VMware Cloud Community
bsmDave
Contributor
Contributor

VCenter upgrade from 6.0 U2a to 6.5

Hi,

I'm trying to upgrade my vcenter server but upgrade stop on pre-upgrade script with error

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

My vcenter runs on WIndows 2012 and db "VCDB" on a different MSSQL 2008 R2

Anyone can help me?

Thanks

3 Replies
RAJ_RAJ
Expert
Expert

Hi ,

There is reference KBs , please have a look , it may help you

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21191...

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21134...

Prepare Microsoft SQL Server Database Before Upgrading to vCenter Server 6.0

vSphere 6.0 Documentation Center

Similar error on 5.5 to 6 .0 discussed on the communitty #

Upgrade from vcenter appliance 5.5.0 to 6.0 database error

RAJESH RADHAKRISHNAN VCA -DCV/WM/Cloud,VCP 5 - DCV/DT/CLOUD, ,VCP6-DCV, EMCISA,EMCSA,MCTS,MCPS,BCFA https://ae.linkedin.com/in/rajesh-radhakrishnan-76269335 Mark my post as "helpful" or "correct" if I've helped resolve or answered your query!
Reply
0 Kudos
Bill_Oyler
Hot Shot
Hot Shot

Hello,

I received the exact same error on (1) of my (3) vCenter 6.0 servers upon upgrade to vCenter 6.5.  The solution was simple: I logged into SQL Management Studio and deleted the extra index "VPX_STAT_COUNTER_M1" in the table called "VPX_STAT_COUNTER".  This worked perfectly and the upgrade to 6.5 was successful.  Note that this was my "lab" vCenter (not production); if you are working on a production vCenter I suggest engaging VMware Support just to be sure this is an acceptable workaround.  This particular lab vCenter has been upgraded in-place from various earlier versions of vCenter, and the SQL DB is quite old, so I'm not surprised we had an extra index.

Bill Oyler Systems Engineer
bsmDave
Contributor
Contributor

Thanks for the suggestion.

I tested the solution in a lab environment, and I have not encountered problems.

I replied in production with satisfactory results!Smiley Happy

Reply
0 Kudos