Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453)

Last Updated: 11/5/2019Categories: TroubleshootingTotal Views: 277175Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

When the rollup jobs are running very slowly as a result of the vCenter Server database size, you may experience these symptoms:

The vCenter Server database is very large (50 GB or more) and the row count in the VPX_HIST_STAT tables is very high (800 million lines or more).

Rollup scripts are running very slowly or may not complete successfully.

Performance Charts may not display recent data.

Gaps are appearing in the Performance Charts.

When this issue is encountered, you may see this error message in the Windows Event Viewer on vCenter Server:

Stats insertion failed for entity esxhost.domain.com due to ODBC error

Cause

This issue occurs due to the stats collection level setting.

Verify the current stats collection level, and if this is set to a collection level higher than 2, then this should be set back to a lower stats collection level of 1.

Resolution

If the vCenter Server database is very large (50 GB or more) and the row count in the VPX_HIST_STAT# table is very high (800 million lines or more), the database rollup scripts may have difficulty handling the amount of data. Rollup scripts run faster if you reduce the size of the vCenter Server database.

Before you reduce the size of the vCenter Server database, you may want to defragment the indexes on your Microsoft SQL database server. For more information, see Defragmenting VMware VirtualCenter or vCenter Server performance data indexes on a Microsoft SQL database (1003990).

Truncating all performance data from vCenter Server 5.x and 6.x

For truncating data in vCenter Server and vCenter Server Appliance 5.x and 6.x, see Delete old tasks, events and statistics data in vCenter Server 5.x and 6.x (2110031)

Reducing the size of the vCenter Server database 2.x

To reduce the size of the vCenter Server database:

Warning: This procedure erases all historical data. If you want to retain some historical performance data instead of deleting all of it, see Delete old tasks, events and statistics data in vCenter Server 5.x and 6.x (2110031)

Ensure that you have a good backup of the vCenter Server database. Do not skip this step.

Shut down the VMware VirtualCenter Server service and any other services (such as VMware VDI or VMware Lab Manager) that use the database. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Note: Again, ensure that you have a recent backup of the vCenter Server database before continuing. Do not skip this step.

Truncate the VPX_HIST_STAT1 table and corresponding VPX_SAMPLE_TIME1 table. After completing the truncate, verify if the rollup jobs are now completing successfully. For more information, see step 4.

Warning: The truncate function is destructive. VMware highly recommends that a Database Administrator perform this step.

To truncate the tables, execute these SQL statements:

truncate table VPX_HIST_STAT1;

Note: In vCenter Server 5.1and 5.5, the table name is VPX_HIST_STAT1_n.

truncate table VPX_SAMPLE_TIME1;

If the rollup jobs do not complete successfully, it may be necessary to truncate the VPX_HIST_STAT2 table, and the corresponding table, VPX_SAMPLE_TIME2. Continue truncating the VPX_HIST_STAT[1-4] tables and corresponding VPX_SAMPLE_TIME[1-4] tables until the rollup jobs are completing successfully.

Note: These additional tables in vCenter Server 4.1 and 5.0 can also be truncated to further reduce the vCenter Server database size. The VPX_TEMPTABLEx tables are a staging/cache area for the performance data before they are processed and moved to VPX_HIST_STAT1.

truncate table VPX_TEMPTABLE0;
truncate table VPX_TEMPTABLE1;
truncate table VPX_TEMPTABLE2;

To run the rollup scripts perform these steps:

Using SQL Management Studio, connect to the SQL database for vCenter Server.

Navigate to SQL Server Agent > Jobs.

Select the individual rollup jobs, right-click and select Start Job at Step.

Start the VMware VirtualCenter Server service and any other service service that you stopped in step 2.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
将 windows vCenter Server 5.5 迁移到 VCSA 6.x 时“缺少索引：VPX_EVENT_ARG、VPX_EVENT_ARG_EVENT_ID (68012)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant