Search the VMware Knowledge Base (KB)
View by Article ID

Workaround for Higher than Expected Values for Capacity Metrics and Badge Scores in vRealize Operations Manager 6.2 (2144413)

  • 0 Ratings


If you installed or upgraded to VMware vRealize Operations Manager 6.2 builds: 3445568, 3445567, 3445569, you may experience higher than expected values for capacity metrics and badge scores.

NOTE: vRealize Operations Manager 6.2 builds 3445568, 3445567, 3445569 were available for download from 28 Jan 2016 to 09 Feb 2016 only. If you did not download or install one of these builds, this KB does not apply to you.

This problem affects derived metrics and their associated historic data. 

To address these problems:

  • Upgrade to the latest version of vRealize Operations Manager 6.2.
  • Edit Active Policies in your vRealize Operations Manager deployment.


Upgrade to the latest version of vRealize Operations Manager 6.2

If you installed one of these version 6.2 builds: 3445568, 3445567 or 3445569, you must download and install the .pak upgrade (build 3528954) from VMware downloads.

For installation and upgrade information, see the vRealize Operations Manager 6.2 Release Notes.

Edit Active Policies

Historical data generated using the original version 6.2 builds 3445568, 3445567 or 3445569 is incorrect. The process to edit active policies changes the time range of the data to be included and removes inaccurate historical data from derived metric calculations. 

Because the new data generated using the latest 6.2.0a .pak upgrade build 3528954 is correct, you adjust the time range to correspond with the number of days since this 6.2.0a .pak upgrade was installed. For example, if the 6.2.0a .pak upgrade was installed two days ago, you set the data range value to 2 or less so that metric calculations will use the data in that time range. As the number of days since you installed the 6.2.0a .pak upgrade increases, you can edit the active policies to increase the data range setting value.

To reset to your original data range setting, wait until that number of days after you installed the 6.2.0a .pak upgrade to make the change. For example, if your original data range setting was 20 days, wait until 20 days after you installed the 6.2.0a .pak upgrade to edit the active policies. If you want to return to the default data range setting, wait 30 days until after you installed the 6.2.0a .pak upgrade.


Use the following procedure to edit the time range for the each of the Active Policies on all vCenter Adapter object types. 
  1. Log in to the vRealize Operations Manager user interface with administrator privileges.
  2. In the left pane of vRealize Operations Manager, click Administration and click Policies. The Active Policies tab appears and lists the policies that are active for the objects in your environment.
  3. Make a note of all Active Policies listed and perform the following steps for all of the policies.
    1. Click the Policy Library tab.
    2. Select an active policy and click the pencil to edit the policy.
    3. Select each object type of the vCenter Adapter under Analysis Settings and perform the following steps:
      1. If the lock icon is in the locked position, click the icon to unlock the Time Range settings.
      2. Change the Data Range to 1 day.
        NOTE: These steps set the data range to one day. You can adjust the data range to fit your upgrade dates. 
    4. Click Save.
For more information about Policy Workspace Analysis Settings, see the vRealize Operations Manager 6.2 Information Center.  

Additional Information

For translated versions of this article, see:

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.


  • 0 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)

Please enter the Captcha code before clicking Submit.
  • 0 Ratings