VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Updating rollup jobs after the error: Performance data is currently not available for this entity

Details

VirtualCenter 2.5 uses SQL Server Agent to run the following SQL Agent jobs to manage historical data:
  • Past Day stats rollup
  • Past Week stats rollup
  • Past Month stats rollup
You may need to setup or recreate SQL agent jobs to manage historical data manually under the following circumstances:
 
  • An upgrade to VirtualCenter 2.5 Server fails to add these jobs.
  • The database is upgraded from SQL Express to SQL Standard or Enterprise.
  • The database is moved to another SQL server.
  • VirtualCenter 2.5 Server is reinstalled and database restored from backup.
  • You try to access performance data for a period other than the last 24 hours and you are presented the message:

    Performance data is currently not available for this entity

Solution

Note: This is a two part solution, please read and understand all of the steps before proceeding. After the jobs are created and enabled properly, they may take a significant amount of time to run.  This article does not apply to installations using Microsoft SQL Server 2005 Express. SQL Server Agent is not available in Microsoft SQL Server 2005 Express. Historic data is managed by the VirtualCenter Server service in this case. 
 

Verifying the existence of jobs and removing them

 
For the scripts to install correctly, you must remove any existing Past _____ stats rollup jobs. This section verifies the existence of jobs and removes them if present. 
 
To verify the existence of jobs and remove them:
  1. Open SQL Management Studio using a Sysadmin account (typically SA or Administrator).
  2. Expand the Server and SQL Server Agent.
  3. Click the Jobs folder. You see a list of all jobs available on your server.

    The following jobs are related to VirtualCenter Server 2.5:
    • Past Day Stats Rollup
    • Past Week Stats Rollup
    • Past Month Stats Rollup
       
  5. Right-click on any of those jobs if they exist and select Delete.
  6. Click OK to confirm the deletion.
  7. Close SQL Management Studio when those jobs are removed.

Adding the SQL Server Agent Jobs

 
This section describes how to install the SQL Server Agent jobs. 
 
To add a SQL Server Agent Job:
  1. Open SQL Management Studio using the database login used by VirtualCenter to connect to the database (typically not SA or Administrator). See Administrative Credentials are required for Oracle and SQL Server databases when installing or upgrading Virtual Center (1003052) to ensure you have the correct permissions.
  2. Click File > Open > File.
  3. Navigate to the location of the jobs:
    • For vCenter 2.5, go to C:\Program Files\VMware\Infrastructure\VirtualCenter Server\dbupgrade\Upgrade-v3-to-v4\PL-SQL\
    • For vCenter 4.0, go to C:\Program Files\VMware\Infrastructure\VirtualCenter Server\
       
  4. Open job_schedule1_mssql.sql.
  5. Ensure that the VirtualCenter Database is selected and that Master is not selected.
  6. Click Execute Query.
  7. Follow Steps 1 to 6 for job_schedule2_mssql.sql and job_schedule3_mssql.sql.
  8. After all three jobs are created, navigate to SQL Server Agent > Jobs in the Object Explorer.
  9. Right-click Past Day stats rollup, then click Properties. Ensure that the owner of the job is the same user as the owner of the database.
  10. Right-click Past Month stats rollup, then click Properties. Ensure that the owner of the job is the same user as the owner of the database.
  11. Right-click Past Week stats rollup, then click Properties. Ensure that the owner of the job is the same user as the owner of the database.  

Oracle

 
To ensure that the scripts are upgraded properly:
  1. Open SQL Plus.
  2. Click File > Open > File.
  3. Navigate to the location of the jobs:

    • For vCenter 2.5, go to C:\Program Files\VMware\Infrastructure\VirtualCenter Server\dbupgrade\Upgrade-v3-to-v4\PL-SQL\
    • For vCenter 4.0, go to C:\Program Files\VMware\Infrastructure\VirtualCenter Server\
       
  4. Open job_schedule1_oracle.sql.
  5. Ensure VirtualCenter Database is selected.
  6. Click Execute Query.
  7. Repeat steps 1-6 for job_schedule2_oracle.sql and job_schedule3_oracle.sql.
  8. After all three jobs are created, ensure that the global Oracle setting JOB_QUEUE_PROCESSES is not set to 0 as this disables all job processing. 
Additional Information
 

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (11 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? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (11 Ratings)   
Actions
  • KB Article: 1004382
  • Updated: Nov 17, 2009
  • Products:
    VMware ESX
    VMware VirtualCenter
  • Product Versions:
    VMware VirtualCenter 2.5.x