VMware vCenter Operations Manager Enterprise 5.0.2

VMware vCenter Operations Manager Enterprise 5.0.2 Release Notes

VMware vCenter Operations Manager 5.0.2 | Build 770500

Last Document Update: 5 July 2012

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

What's New

VMware vCenter Operations Manager Enterprise 5.0.2 includes several new features and changes to existing features.

  • Skip resources for health rollup
    You can now configure vCenter Operations Manager Enterprise to skip the health rollup of a particular resource to the parent resource by setting the skipHealthRollupRKList property in the analytics.properties file. You list the resource kinds that you do not want to be dependent on their children's health in the skipHealthRollupRKList property, for example skipHealthRollupRKList = HostSystem.
  • Filter alerts in the Mashup Charts widget
    Three new icons on the Mashup Charts widget toolbar let you control whether the widget shows only active, only inactive, or all alerts. Inactive alerts appear grey in the display. In addition, the pop-up window that appears when you point to an alert now contains more information about the alert.
  • Configure hint text for KPI alerts
    You can now configure hint text for KPI alerts. The text appears in the HINT field in the Reason pane on the Alert Detail page. See Configuring hint text for KPI alerts in vCenter Operations Manager Enterprise (KB 2021308).
  • Prioritize threshold checking over DT calculation
    You can now pause the dynamic threshold calculation when the data queue size exceeds a certain value by setting the dtBlockIfDataQueueSizeOver property in the vcenter-ops/user/conf/analytics/advanced.properties file, for example, dtBlockIfDataQueueSizeOver=200. This feature lets you prioritize threshold checking over the dynamic threshold calculation. To disable this feature, set the dtBlockIfDataQueueSizeOver property to 0.
  • Configure multi-level alert rules
    You can now configure complex alert rules that evaluate multiple conditions on related resources. See Configuring multi-level alert rules for vCenter Operations Manager Enterprise (KB 2021314).
  • Weight metric groups
    Previously, each metric had equal weight when vCenter Operations Manager Enterprise calculated health. For example, two CPU metrics had the same effect on health as two memory metrics. Now, vCenter Operations Manager Enterprise can calculate the weight of individual metrics based on the number of metrics in the group so that every top-level group has equal weight in the health calculation. When this feature is enabled, the total anomalies metric shows the weighted total anomalies that are related to the total number of metrics. To enable or disable this feature, set the useMetricGroupWeightingForHealth property in the vcenter-ops/user/conf/analytics/analytics.properties file to true or false and restart the Analytics service.
  • View all children of the selected resource in the Alert widget
    Previously, the Alert widget showed only the immediate children of the selected resource. Now, the Alert widget shows all of the children of the selected resource.
  • New Text widget
    You can use the new Text widget to display text in the user interface. The text appears in the Text widget on the dashboard. For information about configuring the Text widget, see Configuring the Text widget in vCenter Operations Manager Enterprise (KB 2030076).

Before You Begin

VMware vCenter Operations Manager Enterprise 5.0.2 is available as a standalone executable and as a vApp that you deploy with the vSphere Client.

You can install and upgrade the standalone version of vCenter Operations Manager Enterprise 5.0.2 on the following operating systems:

  • Windows Server 2003 64-bit SP2 or later
  • Windows Server 2008 64-bit
  • Red Hat Enterprise Linux 5 64-bit

For system requirements, installation instructions, and configuration options for the standalone version, see the VMware vCenter Operations Manager Enterprise Installation and Configuration Guide.

For information about vApp deployments, see the VMware vCenter Operations Manager Deployment and Configuration Guide.

Top of Page

Installation and Upgrade Instructions

To install the standalone version of vCenter Operations Manager Enterprise 5.0.2, run the 5.0.2 installation files for your operating system. For more information, see the VMware vCenter Operations Manager Enterprise Installation and Configuration Guide.

To upgrade from vCenter Operations Manager Enterprise 1.0, 1.0.1, 1.0.2, 5.0, 5.0 Hotfix, or 5.0.1 to 5.0.2:

  1. Depending on the operating system, download the latest .exe or .bin file to the machine where the old product version is installed.
  2. Run the .exe or .bin file.
  3. Select the Reinstall (Upgrade) option.
  4. Select the installation mode.
    • To preserve your settings from the original installation, do not change the default setting..
    • To modify installation options, select Basic or Custom.
  5. On the Database configurations screen, do not modify any settings, and click Finish.
  6. On the main installation screen, click Done.
  7. Check the following log files under the vcenter-ops/user/log folder for upgrade issues:
    • collector.log
    • analytics.log
    • activemq.log
    • controller.log
    • wizard.log
  8. If adapters are installed on the system that you upgraded, download and install the latest adapter versions.
  9. Log in to vCenter Operations Manager Enterprise and verify that the user interface displays properly.

Important: To save time during the standard upgrade procedure, the DB upgrader logic of vCenter Operations Manager Enterprise Standalone does not run the database scripts that handle some specific use cases. For more information, see Configuration wizard does not update the database during an upgrade (KB 2017042).


The vCenter Operations Manager Enterprise 5.0 documentation set contains the following documents:

The vCenter Operations Manager Enterprise 5.0 documentation also applies to vCenter Operations Manager 5.0.2.

Resolved Issues

The following problems have been resolved in this release.

  • Reloading the emailFilter.xml file caused performance problems
    Previously, vCenter Operations Manager Enterprise reloaded the emailFilter.xml file every 30 minutes by default. You could also specify the default reload interval in the FileReloadTimeInMinutes property in the emailFilter.xml file or by typing a value in the File reload time (minutes) text box in the Configuration File Editor. Because the file reload process could cause performance problems, vCenter Operations Manager Enterprise no longer reloads the emailFilter.xml file. The FileReloadTimeInMinutes property has been removed and the File reload time (minutes) text box is no longer effective. If you make changes to the emailFilter.xml file, you must manually restart the plugin to make your changes take effect. To restart the plugin from the vCenter Operations Manager Enterprise user interface, select Admin > Configure Outbound Alert, select the alert plugin instance, and click the Stop and Start icons.
  • Filter email plugin used a generic template even when you configured a custom template
    When you used the Configuration File Editor to add or edit an email template definition, the filter email plugin ignored the template that you specified in the Template text box and used a generic template instead.
  • Adapter Data Source icons did not appear on the Environment Overview page after installing a new adapter and restarting all services
    After you installed a new adapter and restarted all services, vCenter Operations Manager Enterprise did not display icons in the Data Source column of the Environment Overview page for resources collected by the adapter.

Top of Page

Known Issues

This release contains the following known problems.


  • Remote collectors do not work if firewall is enabled
    If a firewall exists between the main vCenter Operations Manager Enterprise server and a remote collector, the remote collector installation fails. Error messages indicate that the heartbeat or ActiveMQ service cannot be reached.
    Workaround: Contact VMware Support Services to discuss workarounds.
  • vCenter Operations Manager Enterprise might stop responding after an upgrade
    vCenter Operations Manager Enteprise might stop responding about a day after an upgrade. Existing user sessions remain open, but you cannot create new login sessions. Views stop responding and data collection stops. This problem occurs because the upgrade process does not check the database deployment and table space configuration. If a third party made custom table space modifications between updates (for example, to improve DBMS performance), the upgrade can place the indexes into the wrong table space and the data table space can exceed its allocated space requirement. This problem can also occur if the default table space becomes full and no modifications are applied between updates.
    Workaround: Use one of the following workarounds, depending on the cause of the problem.
    • After the upgrade, migrate the indexes to the appropriate table space.
    • After the upgrade, revert the database to the default configuration on a larger table space.
  • Installing Microsoft SQL Server with Windows authentication does not work
    You cannot use Integrated Windows Authentication while using Microsoft SQL Server.
    Workaround: The JDBC driver supports the use of Type 2 integrated authentication on Windows operating systems through the integratedSecurity connection string property. To use integrated authentication, copy the sqljdbc_auth.dll file to the vcenter-ops/common/bin folder.
  • You cannot export Anomaly Correlation Reports to a PDF file when vCenter Operations Manager Enterprise is running on a 64-bit server and the browser is Internet Explorer 9
    When you export the Anomaly Correlation Report to the PDF report type, the exported PDF file is 0 bytes.
    Workaround: Make sure that the Do not save encrypted pages to disk option in Internet Explorer is disabled. To disable this option, select Tools > Internet Options > Advanced and deselect the Do not save encrypted pages to disk check box in the Security area under Settings.
  • vCenter Operations Manager Enterprise displays characters of high ASCII as question marks when connected to an Oracle database with the default character setting
    For example, if dashboards or resource tags that have high ASCII characters in their names, those letters appear as question marks (?).
    Workaround: Configure the Oracle database to use a Unicode character set such as UTF-8 to make characters display correctly.
  • Cyclic redundancy check (CRC) errors manifest as missing data
    CRC errors appear as missing data for a given resource.
    Workaround: Check the vcenter-ops/data/vcops/log/analytics.log file to see if CRC-related errors are logged, for example:

    com.integrien.alive.FSDB.FSDBException: CRC Failure in file for Resource 6773, filename = /data/vcops/data/6/6773/2011_10_6773.dat
    2011-11-11 03:04:31,552 ERROR [Calc DT worker thread 3]
    com.integrien.analytics.datareceiver.MetricDataRetriever.getDataPointBundle - CRC Failure in file for Resource 6773, filename = /data/vcops/data/6/6773/2011_10_6773.dat

    If the log file contains CRC-related errors, set the FSDBCheckAndRepair property to 2 in the vcenter-ops/user/conf/analytics/advanced.properties file. Errors are corrected within seven days.

  • You must update the statistics of data tables periodically so that the Oracle SQL native query analzyer can operate and fetch data efficiently
    vCenter Operations Manager Enterprise does not provide a user interface to configure database updates.
    Workaround: See Automated gathering of statistics for Oracle database tables and their indexes (KB 2016451).


  • Administration Guide does not describe MIB file for SNMP traps
    You can configure vCenter Operations Manager to send alert notifications as SNMP traps. The vcenter-ops/user/plugins/outbound/snmp_alertplugin/mibs/VMWARE-VCOPS-EVENT_MIB.mib file contains the information that you need to enable the receiving party to interpret these traps.
  • Administration Guide does not describe how to suppress No Data Receiving alerts
    To configure an adapter instance not to generate alerts when it is not receiving data:
    1. Open the vcenter-ops/user/conf/analytics/advanced.properties file.
    2. Add the disabledNoDataReceivingAlertIds = resourceID property.
      resourceID is the resource ID of the adapter instance.
    3. Save your changes and close the advanced.properties file.
    4. Restart the Analytics service for your changes to take effect.
  • Online help describes nonexistent Resolution tab
    The Resolution tab was removed from the user interface, but it is still described in the online help.
  • Administration Guide describes nonexistent emailFilter.xml file option
    The option to set the reload interval for the emailFilter.xml file (FileReloadTimeInMinutes property and File reload time (minutes) text box in the Configuration File Editor) was removed from the user interface, but it is still described in the administration guide.
  • Documentation and online help do not describe the new features for the 5.0.2 release
    The documentation and online help were not updated for the 5.0.2 release. For descriptions of the new features, see What's New.

Top of Page