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

Updating the VMware vRealize Operations Manager (formerly known as VMware vCenter Operations Manager) database by using scripts instead of the Configuration wizard (2017042)

  • 7 Ratings


To save time during the standard upgrade procedure, the DB Upgrader logic of vRealize Operations Manager Enterprise (formerly known as VMware vCenter Operations Manager (Standalone)) does not run the database scripts in the following situations.

  • The upgrade requires schema modifications, and the DB credential for vRealize Operations Manager has insufficient privileges to run the schema upgrade script.
    Currently you cannot provide external credentials and cannot run the upgrade script externally.
  • Database modification requires a long time. For example, creating indexes on large tables may require a considerable amount of time.
  • Currently, you cannot run the upgrade script before the scheduled upgrade operation.

You can use the attached scripts to update the database manually instead of using the vRealize Operations Manager Configuration wizard under the following circumstances.

  • If the Configuration wizard fails during the upgrade procedure.
  • If the database contains a large number of records.


Run the scripts in the attached ZIP archive to address these problems and upgrade the database.

  1. Verify that you have the required privileges to run the scripts on the database. For example, Oracle databases require CREATE PROCEDURE privilege for the user.

  2. On the vRealize Operations Manager server machine, stop all vRealize Operations Manager services.

  3. Select the set of scripts that corresponds to the database type.

    Inside the MSSQL or the Oracle folder, select a folder as follows:

    • Open the Upgrade to 50 folder if you are upgrading from vRealize Operations 1.0 or 1.0.1.
    • Open the Upgrade to 501 folder if you are upgrading from vRealize Operations 1.0, 1.0.1, 1.0.2, or 5.0.
    • Open the Upgrade to 502 folder if you are upgrading from vRealize Operations 5.0.1.
    • Open the Upgrade to 503 folder if you are upgrading from vRealize Operations 5.0.2.
    • Open the Upgrade to 56 folder if you are upgrading from vRealize Operations 5.0.3.

  4. Run the scripts that you need on the vRealize Operations Manager schema.

    • MSSQL
      • upgrade to 50
        add_missing_fk_indexes_MSSQL.sql - Adds indexes on tables and columns that are referenced to another table as a foreign key.
      • upgrade to 501
      • upgrade to 502
      • upgrade to 503
      • upgrade to 56
      • upgrade to 57

    • Oracle
      • upgrade to 50
        make_fk_constraints_deferrable_Oracle.sql - Makes all foreign keys deferrable. Deferrable keys are used by the vRealize Operations Manager code for optimization.
      • upgrade to 501
      • upgrade to 502
      • upgrade to 503
      • upgrade to 56
      • upgrade to 57

  5. On the vRealize Operations Manager server machine, start all vRealize Operations Manager services.

Note: To upgrade the database from an earlier version to the latest version, you must run all scripts consecutively. For example, to upgrade the database from vRealize Operations Manager 5.0 to 5.0.3, you must run the scripts for 5.0 to 5.0.1, then the scripts for 5.0.1 to 5.0.2, and then the ones for 5.0.2 to 5.0.3 upgrade.

To be alerted when this article is updated, click Subscribe to Document in the Actions box.


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.


  • 7 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.
  • 7 Ratings