Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

vRealize Automation upgrade fails due to duplicates in the vRealize Orchestrator database (54987)

Last Updated: 8/18/2023Categories: TroubleshootingTotal Views: 11868Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Details

When upgrading vRealize Automation appliances, you may experience failures related to duplicates in the database for the vRealize Orchestrator service.

In the vRealize Automation VAMI UI, you see the failure messages similar to :
Failed to install updates(Error while running post-install scripots)
VA-check: finished
Pre-install: finished
Post-install: failed
Update failed (code 0-2). Check logs in /opt/vmware/var/log/vami or retry update later.

In the /var/log/bootstrap/postupdate.log file, you see the entries similar to:

Orchestrator Configuration Tool. Version: 7.4.0.8071781 Build: 8071781

Can not read the Orchestrator pid from /var/lib/vco/app-server/logs/tomcat.pid
Start configuring database settings.
Configuring database settings finished successfully.
Start updating database scheme.
ch.dunes.vso.db.check.CheckDuplicatesException:
Duplicate entries found in the Orchestrator database:

System tables duplicates:
2 items with ID '<UUID>' in database table 'vmo_scriptmodulecontent'
.
.

Resolve duplicates by deleting unnecessary items.
java.lang.RuntimeException: ch.dunes.vso.db.check.CheckDuplicatesException:
Duplicate entries found in the Orchestrator database:

Resource element duplicates:
1 item with ID '<UUID>' and name 'ko.properties'
1 item with ID '<UUID>' and name 'fr_FR.properties'
1 item with ID '<UUID>' and name 'zh_CN.properties'
(and many more)

vRealize Automation 7.5+:

Duplicates found in the embedded vRealize Orchestrator database:

- 1 items in table vmo_configelement: ID=8a81a5a35f107593015f7871f8da0431 NAME=InstanceDetails

- 1 items in table vmo_configelement: ID=8a81a5a35f107593015f7871f8da0431 NAME=General

- 1 items in table vmo_configelement: ID=8a81a5a35f107593015f7871f8da0431 NAME=Allocation

Script /etc/bootstrap/preupdate.d/00-00-02-check-vro-duplicates failed, error status 1

Solution

VMware is aware of this issue.

A resolution for this issue is being evaluated for inclusion in a future release.

To work around this issue when vRO is using the embedded vRA psql database, perform the following steps:

For vRealize Automation 7.0 - 7.4:

Revert vRealize Automation environment back to pre-upgrade snapshots including IaaS components and SQL Database.

Ensure you have proper backups of the environment prior to proceeding!

Download the attached zip file and extract the contents.

Copy the vco-cfg-cli-7.4.0.23640-8992942.noarch.rpm  file to a directory on your vRealize Automation appliance.

Install the package using the command:

rpm -hiv vco-cfg-cli-7.4.0.23640-8992942.noarch.rpm

Run the command:

/usr/lib/vco-cli/bin/vro-configure.sh db-validate

Copy the list of duplicate entries (focused on id and name) for reference.

Connect to the postgres database using the command:

su postgres

/opt/vmware/vpostgres/current/bin/psql vcac

Run the following command(s) by referencing the correct ID and NAME from step 7 to remove one of each of the duplicate entries (it doesn't matter which is removed):

delete from vmo_resourceelement where categoryid = 'cbd45656-bfb7-3275-8c1c-7ab8aa6ee487' and name = 'de_DE.properties'; ​

delete from vmo_configelement where categoryid = 'cbd45656-bfb7-3275-8c1c-7ab8aa6ee487' and name = 'de_DE.properties';

Exit the postgres command using: \q

Re-run the command to ensure you have no further duplicates:

/usr/lib/vco-cli/bin/vro-configure.sh db-validate

The correct response should be:

The command does not need a database configuration update.

Create additional backups/snapshots and retry your vRealize Automation upgrade.

For vRealize Automation 7.5+:

In 7.5 and 7.6 the upgrade automatically checks for duplicates and reports on those tables that are duplicates. Once duplicates are found you need to delete the duplicates. You may run the below command to check after deletion that all tables are removed.

Check for duplicate elements in versions 7.5+:

cd /usr/lib/vco/tools/configuration-cli/bin/

command : ./vro-configure.sh db-validate

If there are no duplicates you should see something to the below:

Orchestrator's root folder: /var/lib/vco

Orchestrator Configuration Tool. Version: 7.6.0.12923317 Build: 12923317

ValidateDbOptions{dbUsername='vmware', dbPassword='****', jdbcUrl='jdbc:postgresql://localhost:5433/vmware?sslmode=verify-ca&sslrootcert=/var/vmware/vpostgres/current/.postgresql/root.crt'}

The command does not need database configuration update.

If duplicates are found there should be three primary types: Plugins, Version History, and Configuration Elements.  See below for instructions for each:

Plugins are flagged as duplicate:

Login to Orchestrator Client as Design user.

Enter the Name output in the output in the NAME field output by upgrade.

Open each duplicate and make note of the one with the most relevant content that you wish to keep.

Right Click on the one you wish to remove and delete.

Version history is flagged as duplicate:

Login to the Orchestrator Client

Resolve duplicates by deleting unnecessary items

Note: The auto-creation of an item means there is a running vRO process connected to your database. You must stop it and then delete the duplicate entry. The missing version history items are not critical and even they miss in different situations so it is not that important which one gets deleted.

Example:
Duplicates found in the embedded vRealize Orchestrator database:

- 1 items in table vmo_versionhistorycontent: ID= NAME=1.0.800

- 1 items in table vmo_versionhistorycontent: ID= NAME=-1.0

Configuration elements are flagged as duplicate:

Login to the Orchestrator Client

Search for the GUID

Remove the duplicate element.

Example:
Duplicates found in the embedded vRealize Orchestrator database:

- 1 items in table vmo_configelement: ID=8a81a5a35f107593015f7871f8da0431 NAME=InstanceDetails

- 1 items in table vmo_configelement: ID=8a81a5a35f107593015f7871f8da0431 NAME=General

- 1 items in table vmo_configelement: ID=8a81a5a35f107593015f7871f8da0431 NAME=Allocation

Script /etc/bootstrap/preupdate.d/00-00-02-check-vro-duplicates failed, error status 1

Corrupted, duplicate workflow tokens:

Download the attached workflow package: com.vmware.o11n.bug_2444547.package

Import the package

Setup the /storage/db/pgdata/pg_hba.conf file to allow local connections from source IP:

Under heading: # IPv4 local connections:

Add the IP address of the vRealize Orchestrator node that will need access to the postgres database:

Example:

host all all 192.168.110.75/24 md5

Restart vpostgres:

service vpostgres restart

Extract PSQL password and decrypt:

cat /etc/vcac/server.xml |grep password="*"

/usr/lib/vcac/tools/config/bin/vcac-config prop-util -d --p s2enc~646fCCJWPaSYJe91XKBpkrc1E+3N83n7ZIF3a+PGEaI= |less

Example password Output:

gRhoeG3+76n2o*nS 

Create a new SQL Plugin host connection within the vRealize Orchestrator client by running the workflow named: "Library > SQL > Configuration > Add a database"

Name: "Local vPostgres Instance"

Database Type: postgreSql

Connection URL: jdbc:postgresql://vra-01.vcloud.local:5432/vcac

Select "Next"

Session Mode: "Shared Session"

User name:  vcac

Provide decrypted credentials, example: gRhoeG3+76n2o*nS

Execute the workflow: "Delete Corrupted WorkflowTokens"

Note:  If the workflow fails, comment out: // System.log(token.state);
from within the Scriptable task object within the workflow "Delete Corrupted WorkflowTokens"

Reattempt the upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

54987_1_vco-cfg-patch

com.vmware.o11n.bug_2444547

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.x

VMware vRealize Automation 6.2.x

Take Our Survey

Support Assistant