VMware vCenter Operations Manager Installable 5.6

VMware vCenter Operations Manager Installable 5.6 Release Notes

VMware vCenter Operations Manager 5.6 | Build 923460

Last Document Update: 21 DECEMBER 2012

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

What's New

The VMware vCenter Operations Manager 5.6 release is an update to the vCenter Operations Manager 5.x releases. vCenter Operations Manager 5.6 includes new features, enhancements, and product integrations.


The vCenter Operations Manager 5.6 user interface and online help are available in Simplified Chinese, German, and Japanese. The vCenter Operations Manager 5.6 documentation set is also available in these languages.

Product Compatibility

Refer to the VMware Compatibility Guide for more information about VMware certified compatibility for vCenter Operations Manager: http://www.vmware.com/resources/guides.html.

The VMware vCenter Operations Manager Installation and Configuration Guide for Windows and Linux lists compatible versions of vSphere and other components that vCenter Operations Manager supports.

vCenter Operations Manager 5.6 supports the following browsers.
  • Internet Explorer for Windows 8.0 and 9.0
    Note: The Compatibility View mode must be disabled.
  • Mozilla Firefox 3.6 and above

The minimum supported browser resolution is 1024 by 768 pixels.

Before You Begin

VMware vCenter Operations Manager version 5.6 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 5.6 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 Installation and Configuration Guide for Windows and Linux.

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 5.6, run the 5.6 installation files for your operating system. For more information, see the VMware vCenter Operations Manager Enterprise Installation and Configuration Guide for Windows and Linux.

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

    Note: The database upgrade may fail if you have insufficient privileges. The minimum permissions and privileges required to upgrade the database are: CREATE TABLE, CREATE TRIGGER, CREATE SEQUENCE, CREATE SESSION, and CREATE PROCEDURE.
  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 (Custom UI) and verify that the user interface displays properly.

Important: To save time during the standard upgrade procedure, the database upgrader logic of vCenter Operations Manager Installable 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 Custom UI 5.6 documentation set contains the following documents:

Top of Page

Known Issues

This release contains the following known problems.


  • Tomcat server does not start after upgrading to vCenter Operations Manager 5.6
    The Tomcat server fails to start and generates an exception similar to "SEVERE: Exception starting filter struts Unable to load configuration. - [unknown location]" This problem occurs when InstallAnyWhere could not remove the old .jar files and there is a conflict between the old and new .jar files.
    Workaround: Find the conflicting struts .jar files in $ALIVE_BASE/tomcat/webapps/ROOT/WEB-INF/lib/, remove or rename the old .jar files, and restart the Tomcat server. For example, rename or remove old $ALIVE_BASE/tomcat/webapps/ROOT/WEB-INF/lib/struts2-core- file to resolve the conflict with a newly installed $ALIVE_BASE/tomcat/webapps/ROOT/WEB-INF/lib/struts2-core- file.
  • vCenter Operations Manager (Custom UI) might stop responding after an upgrade
    The vCenter Operations Manager Custom UI 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 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.
  • Disk Space metrics collection fails after upgrading vCenter Operations Manager
    Disk Space metric collection from vCenter Storage Monitoring Service might fail after upgrading from vCenter Operations Manager version 1.0.x to version 5.6. This failure can lead to missing disk space metrics and scores for the Risk and Efficiency badges.
    Workaround: Find and remove the file vijava2120100715.jar under $ALIVE_BASE/user/plugins/inbound/vmwarevi_adapter3/lib/ and restart the collector or vCenter Operations Manager services.
  • vCenter Operations Manager (Custom UI) 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.
  • Exception occurs when you perform a search on the Environment Overview page
    The message "Error 'Could not execute query' in the UI, and Exception in the web.log" occurs when you perform a search on the Environment Overview page in the Custom user interface. This problem is caused by a known issue in Oracle 10g.
    Workaround: For pre-11gR2 databases, set cursor sharing to 'EXACT' (the default setting). For 11gR2 and later databases, no changes are required and the problem is resolved in 11gR2 Fixpack 2 (
  • Installing vCenter Operations Manager Standalone with MS SQL in console mode on Linux fails to test the database connection
    Testing the database configuration will fail due to .RSA and .SF file inconsistencies when the configuration wizard is run from InstallAnywhere, but this failure doesn't impede the overall installation process.
    Workaround: This failure can be ignored. The installation is successful afterwards. If the user wants to test the database connection which failed during setup, the configuration wizard can be run from the bash shell using the "$HOME/Configure_VMware_vCenter_Operations -i console" command.
  • 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 analyzer can operate and fetch data efficiently
    The vCenter Operations Manager Custom UI 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).
  • The result of getBusinessServiceConfigAsXml does not contain resource identifiers
    This might cause problems interpreting the result of the API call since resources might not be uniquely identified.
    1. The getBusinessServiceConfigAsXml method returns an XML string containing business service configuration. The resource tag in the result does not contain identifiers. This is a limitation with no workaround. As a result, the XML received from getBusinessServiceConfig call posted to the configBusinessService method might not produce the same result, as configBusinessService now requires identifiers to be present.
    2. The background issue is that in 5.6 configBusinessService was fixed to take into account resource identifiers. This behavior is consistent with the product logic and documentation. It might brake existing client applications that used to call the API in a different way. Before the fix, the API method only used resource name for identification and could produce inaccurate results by adding all resources with a matching name into specified tiers.

    Workaround: Specify identifiers as part of the configBusinessService call. If identifiers are unknown, they can be looked up using the lookupResource API call before being added into the business service config XML.


The following product changes were not described in the release documentation.
  • VMWARE-VCOPS-EVENT-MIB.mib file changed
    The VMWARE-VCOPS-EVENT_MIB.mib file contains information that the receiving party needs to interpret the SNMP traps that vCenter Operations Manager (Custom UI) sends. The Object Identifier (OID) for vCenter Operations Manager (Custom UI) is changed from 19004 to 6876 in this MIB file.
  • New menu next to Search on Environment Overview page
    A new drop-down menu has been added next to the Search text box on the Environment Overview page in the Custom user interface. You can use this drop-down menu to select a column name and search by column, or you can select All to search all columns. For example, you can select Name to search the Name column.
  • All and group options for dashboard commands
    For the dashboard import, dashboard delete, and dashboard reorder commands, you can use one of the following options instead of specifying a user name:
    * --all
    * --group:<group_name[,<group_name>]

    The --all option applies the command to all user accounts. The --group:<group_names[,<group_name>] option applies the command to all user accounts that belong to the specified user groups. For example, the command dashboard import group:Administrators,Operators "templates\MyDashboard.bin" imports the dashboard MyDashboard.bin to all user accounts that belong to the Administrators and Operators user groups.

    The dashboard import command also has a --set <rank> option that enables you to set the dashboard order. For example, the command dashboard import MyUser2 "dashboards/MyDashboard.bin" --set 1 imports the dashboard MyDashboard.bin and makes it the first dashboard in the dashboard list for the user MyUser2.
  • Missing information on consolidated alerts in the Custom UI documentation
    See Aggregating and Filtering Alerts in vCenter Operations Manager 5.6 (Custom UI) (KB 2039020) for details.

Top of Page