• 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:

For vRealize Automation 7.0 - 7.4:

1. Revert vRealize Automation environment back to pre-upgrade snapshots including IaaS components and SQL Database.
2. Ensure you have proper backups of the environment prior to proceeding!
3. Download the attached zip file and extract the contents.
4. Copy the vco-cfg-cli-7.4.0.23640-8992942.noarch.rpm  file to a directory on your vRealize Automation appliance.
5. Install the package using the command: 

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

6. Run the command:  

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

7. Copy the list of duplicate entries (focused on id and name) for reference.
8. Connect to the postgres database using the command:
   • su postgres
   • /opt/vmware/vpostgres/current/bin/psql vcac
9. 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';
10. Exit the postgres command using: \q
11. Re-run the command to ensure you have no further duplicates:  

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

12. The correct response should be: 

    • The command does not need a database configuration update.

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

For vRealize Automation 7.5+:

1. Check for duplicate elements in versions 7.5+:

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

3. If duplicates are found there should be three primary types: Plugins, Version History, and Configuration Elements.  See below for instructions for each:
   1. Plugins are flagged as duplicate:
      1. Login to Orchestrator Client as Design user.
      2. Enter the Name output in the output in the NAME field output by upgrade.
      3. Open each duplicate and make note of the one with the most relevant content that you wish to keep.
      4. Right Click on the one you wish to remove and delete.
   2. Version history is flagged as duplicate:
      1. Login to the Orchestrator Client
      2. Resolve duplicates by deleting unnecessary items

3. Configuration elements are flagged as duplicate:
   1. Login to the Orchestrator Client
   2. Search for the GUID
   3. Remove the duplicate element.

4. Corrupted, duplicate workflow tokens:
   1. Download the attached workflow package: com.vmware.o11n.bug_2444547.package
   2. Import the package
   3. Setup the /storage/db/pgdata/pg_hba.conf file to allow local connections from source IP:
      1. Under heading: # IPv4 local connections:
      2. Add the IP address of the vRealize Orchestrator node that will need access to the postgres database:
         Example:

3. Restart vpostgres:

4. Extract PSQL password and decrypt:

4. 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

4. Execute the workflow: "Delete Corrupted WorkflowTokens"

5. Reattempt the upgrade.