Académique Documents
Professionnel Documents
Culture Documents
1 of 5
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&ext...
Knowledge Base
Updating rollup jobs after the error: Performance data is currently not available for this entity (1004382)
Details
VirtualCenter 2.5, vCenter Server 4.x and vCenter Server 5.x use SQL Server Agent to run these SQL agent jobs to manage historical data:
Past Day stats rollup
Past Week stats rollup
Past Month stats rollup
Process Performance Data myDB
You may need to set up or recreate SQL agent jobs to manage historical data manually under these circumstances:
An upgrade to VirtualCenter 2.5, vCenter Server 4.x or vCenter Server 5.x 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 or vCenter Server 4.x 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 with this message:
Performance data is currently not available for this entity
Windows Event Viewer on vCenter server shows an entry similar to:
EventTypeId: com.vmware.vc.stats.StatsInsertErrorEvent
FullFormattedMessage: Stats insertion failed for entity esxhost.domain.com due to ODBC error.
Note: For more information about SQL agent jobs for VMware vCenter Server 5.x, see Verifying jobs and stored procedures installed in vCenter Server 5.0 (2006097) (/selfservice/search.do?cmd=displayKC&docType=kc&
docTypeID=DT_KB_1_1&externalId=2006097) and Verifying jobs and stored procedures installed in vCenter Server 5.1 and 5.5 (2033096) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2033096)
Solution
Note: This is a two-part solution. 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. Historical data is managed by the VirtualCenter Server service in this
case. In addition, the DSN account must have the correct permissions to run the rollup jobs. If the account does not have the correct permissions, the performance data is not collected. This can be seen in the logs
for the rollup jobs.
1/24/2015 8:35 PM
VMware KB: Updating rollup jobs after the error: Performance data is currently not available for...
2 of 5
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&ext...
Note: Ensure to take a backup of the vCenter Server database before proceeding.
1/24/2015 8:35 PM
VMware KB: Updating rollup jobs after the error: Performance data is currently not available for...
3 of 5
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&ext...
7. Copy the query outlined in job_schedule1_mssql.sql to the New Query pane in SQL Management studio, then click Execute Query.
8. Repeat steps 1 to 7 for:
job_schedule2_mssql.sql
job_schedule3_mssql.sql
job_dbm_performance_data_DB.sql
job_cleanup_events_DB.sql
job_property_bulletin_DB.sql
job_topn_past_day_DB.sql
job_topn_past_month_DB.sql
job_topn_past_week_DB.sql
job_topn_past_year_DB.sql
Note: for vCenter Server 5.1 and 5.5, see Verifying jobs and stored procedures installed in vCenter Server 5.1 and 5.5 (2033096) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&
externalId=2033096)
(http://ikb.vmware.com/contactcenter/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2033096)
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, then copy the contents of job_schedule1_oracle.sql:
VirtualCenter 2.5: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\dbupgrade\Upgrade-v3-to-v4\PL-SQL\
vCenter Server 4.x: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\sql
vCenter Server 5.x: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\sql
4. Open an SQL Plus session with a user account that has access to the Oracle tables, jobs, and schedules related to the vCenter Server.
5. Execute the job_schedule1_oracle.sql script.
Note: Contact your Oracle database administrator or see Oracle support documentation for information on how to execute Oracle scripts.
6. Repeat steps 1-5 for job_schedule2_oracle.sql and job_schedule3_oracle.sql.
7. 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. To show this parameter setting, run the query:
select value from v$parameter where name='job_queue_processes';
Additional Information
1/24/2015 8:35 PM
VMware KB: Updating rollup jobs after the error: Performance data is currently not available for...
4 of 5
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&ext...
If you encounter issues after upgrading to vCenter Server 4.0, see Past Week stats rollupvc40 SQL Server job fails to complete after upgrading to vCenter (1014209) (/selfservice/search.do?cmd=displayKC&docType=kc&
docTypeID=DT_KB_1_1&externalId=1014209) .
See Also:
Verifying vCenter Server 2.5 jobs and stored procedures (1033588) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1033588)
Verifying vCenter Server 4.0 jobs and stored procedures (1033587) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1033587)
Verifying vCenter Server 4.1 jobs and stored procedures (1029824) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1029824)
Verifying jobs and stored procedures installed in vCenter Server 5.1 and 5.5 (2033096) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2033096)
Verifying jobs and stored procedures installed in vCenter Server 5.0 (2006097) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2006097)
Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1007453)
Performance data is currently not available for this entity (2001955) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&
externalId=2001955)
Portugus:
: Performance data is currently not available for this entity (2001955) (/selfservice/search.do?cmd=displayKC&docType=kc&
docTypeID=DT_KB_1_1&externalId=2001955)
: (2077750)
(/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2077750)
Tags
performance-statistics-rollup vcenter-database-rollup-jobs-fail
Update History
04/20/2010 - Added vCenter Server 4.0 to Products.
01/25/2012 - Added link to information about SQL agent jobs in vSphere 5.0.
04/20/2012 - Added new Step 9 to SQL jobs section
03/05/2013 - Added note for Step 9
04/08/2013 - Added note to back up vCenter Server database
10/08/2013 - Title change to KB 2033096.
11/11/2013 - Added vCenter Server 5.5 to Products.
Follow us (http://www.twitter.com/vmwarekb)
content-request.html)
1/24/2015 8:35 PM
VMware KB: Updating rollup jobs after the error: Performance data is currently not available for...
5 of 5
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&ext...
1 (javascript:void( rate(1,this) ))
2 (javascript:void( rate(2,this) ))
3 (javascript:void( rate(3,this) ))
4 (javascript:void( rate(4,this) ))
5 (javascript:void( rate(5,this) ))
129 Ratings
Actions
KB: 1004382
Updated: Oct 15, 2014
Categories:
Troubleshooting
Languages:
English
Product(s):
VMware ESX
VMware VirtualCenter
VMware vCenter Server
Product Version(s):
VMware ESX 3.0.x
VMware ESX 3.5.x
VMware ESX 4.0.x
VMware ESX 4.1.x
VMware VirtualCenter 2.5.x
VMware vCenter Server 4.0.x
VMware vCenter Server 4.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.5.x
1/24/2015 8:35 PM