Upgrading vRA from 6.2.5/7.x to 7.4 fails due to duplicate entities in vRO DB
Article ID: 317099
Updated On:
Products
VMware Aria Suite
Issue/Introduction
This article helps to resolve the problem that may happen during vRA upgrade from 6.2.5/7.x to 7.4 release.
Symptoms:
vRA upgrade fails from 6.2.5/7.x to 7.4 due to duplicate entities in vRO DB.
Symptoms:
vRA upgrade fails from 6.2.5/7.x to 7.4 due to duplicate entities in vRO DB.
Environment
VMware vRealize Automation 7.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation 6.2.x
Cause
This issue occurs due to duplicate entries which may exist in the embedded vRO database.
Resolution
To resolve this issue, execute the below mentioned steps before upgrade of vRA appliance to version 7.4.
Common cases:
Case 1:
- Backup your vRA database.
- Download rpm package attached to this article. (Filename: vco-cfg-cli-7.4.0.23640-8992942.rpm)
- Install rpm package: rpm -hiv vco-cfg-cli
- Execute: /usr/lib/vco-cli/bin/vro-configure.sh db-validate
- Check command output. If duplicate entities exists in the vRO database then command output will point details about these entities.
In case duplicate entities exists in vRO database then check these entities and make a decision to rename or remove them. If these entities are managed by vRO client then these entities will be visible in the client if you rename them.
Common cases:
Case 1:
In case you have horizon-view plugin installed on your vRO, then you will have the below listed duplicated entities:
--------------------------------------------------------------------------------------------------------------------------------------------------
Duplicate entries found in the Orchestrator database:
Resource element duplicates:
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'zh.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'zh_HK.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'fr_FR.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'ko.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'de_DE.properties'
Resolve duplicates by deleting unnecessary items:
--------------------------------------------------------------------
If this is the case, then remove or rename duplicated entities for every resource element from 'vmo_resourceelement' table.
--------------------------------------------------------------------------------------------------------------------------------------------------
Duplicate entries found in the Orchestrator database:
Resource element duplicates:
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'zh.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'zh_HK.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'fr_FR.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'ko.properties'
1 item with categoryid 'ff808081632cbcdb01632cc15b7b01f9' and name 'de_DE.properties'
Resolve duplicates by deleting unnecessary items:
--------------------------------------------------------------------
If this is the case, then remove or rename duplicated entities for every resource element from 'vmo_resourceelement' table.
Case 2:
In case you have a duplicate elements in table 'vmo_scriptingmodulecontent' then check xmlcontent of every duplicate record and delete those of them, which are having incorrect content (for ex. empty or duplicate xml content).
In case you have a duplicate elements in table 'vmo_scriptingmodulecontent' then check xmlcontent of every duplicate record and delete those of them, which are having incorrect content (for ex. empty or duplicate xml content).
- After removing duplicate entries execute step 4 to validate that duplicate entries does not exists any more.
- Proceed with vRA upgrade.
Attachments
Feedback
Yes
No
Powered by
