Set the
VPX_U1 index to case sensitive in the vCenter Server database to resolve performance data issues after upgrading vCenter Server to 6.0.
Symptoms:
- New performance data is not collected after upgrading vCenter Server from 5.x to 6.0.
- In the performance data charts, you see this error:
Performance data is currently not available for this entity
Note: For additional symptoms and log entries, see the Additional Information section. - From vCenter Server 5.x with external MSSQL who have configured statistics at level 3 or higher, would not see any new data coming in.
Similar error messages is seen in vpxd log files:
2015-07-09T03:58:05.015+02:00 error vpxd[07000] [Originator@6876 sub=StatsCollector] Flush failed. Error : "ODBC error: (23000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot insert duplicate key row in object 'dbo.vpx_device' with unique index 'VPX_DEVICE_U1'. The duplicate key value is (host/system/ft)." is returned when executing SQL statement "INSERT INTO VPX_DEVICE( DEVICE_ID, DEVICE_NAME) VALUES(?,?)"^M