The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Rollup stored procedures in Microsoft SQL fail after upgrading from vCenter Server 4.1 to vCenter Server 4.1 Update 3 (2030365)
After upgrading from vCenter Server 4.1 to vCenter Server 4.1 Update 3, you experience these symptoms:
- Stats/performance data fails to roll up
- Rollup stored procedures (past day/week/month) in MS SQL fail
- If the vCenter Server installations uses the bundled database, the vpxd-*.log files report this error when running the rollup stored procedures:
[2012-01-30 17:32:54.347 07744 error 'App'] [VpxdStatsAggregator] Error during
"ODBC error: (22003) - [Microsoft][SQL Server Native Client 10.0][SQL
Server]"Arithmetic overflow error converting varchar to data type int" is
returned when executing SQL statement "stats_rollup1_proc"
- If the vCenter Server installation uses an external database, the job status indicates that the store procedure did not complete successfully
VMware is aware of this issue.
Incorrect data cast in the stored procedure causes the rollup procedures to fail after the upgrade. The correct stored procedures are bundled with vCenter Server 4.1 Update 3.
To work around this issue, you may replace the following affected stored procedures in the MS SQL database.
The scripts may be found under vCenter Server install directory. Default location is C:\Program Files\VMware\Infrastructure\VirtualCenter Server
For instructions to replace the stored procedure on SQL Server, see Replacing the Existing Statistics Rollup Stored Procedure (1001420).
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.