Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Historical performance data in vCenter Server does not get saved (2011523)

Cause

This issue occurs if the following tables are locked: 
  • vpx_temptable0
  • vpx_temptable1
  • vpx_temptable2 
 
These tables are a buffer area for the performance data before they are processed by the database rollup jobs. If these temptables are locked, there is nowhere to place the historical performance data and, as a result, the data will be lost.

Resolution

 This is a known issue in vCenter Server 4.1.
 
This issue is resolved in vCenter Server 5.0 Update 1. For more information, see the VMware vCenter Server Update 1 Release Notes.

Caution: Ensure that the process_temptable#_proc stored procedures are not running before performing any of the steps below.
 To replace the statistics and purge the stored procedure in your vCenter Server database, complete the steps in this workaround: 
 
  1. Stop the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
  2. Download 2011523_ process_temptable_proc_mssql.zip (attached to this article).
  3. In your database client utility (SQL Server Query Analyzer or SQL Server Management Studio), connect to your SQL Server database using credentials that vCenter Server uses to connect.
  4. Open a new query window.
  5. Click the vCenter Server database.
  6. Run these commands at the SQL prompt:

    DROP PROCEDURE process_temptable0_proc;
    DROP PROCEDURE process_temptable1_proc;
    DROP PROCEDURE process_temptable2_proc;

  7. Extract the contents of 2011523_process_temptable_proc_mssql.zip.
  8. Copy and paste the extracted contents of the file into the new query window.
  9. Click Execute. When the procedure is updated, this message appears:

    Command(s) completed successfully
  10. Repeat step 7 with the files process_temptable1_proc_mssql.sql and process_temptable2_proc_mssql.sql.
  11. Start the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Notes: If invalid object name displays when you run the update scripts, verify that:

  • The SQL login is the one used by vCenter Server, not sa or Administrator.
  • The current database is the vCenter Server database, not master or some other database.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

06/08/2012 - Added resolved by in resolution.

Attachments

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.

Feedback

  • 6 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 6 Ratings
Actions
KB: