Embedded vRealize Orchestrator appliance database type is changed to something other than PostgreSQL
search cancel

Embedded vRealize Orchestrator appliance database type is changed to something other than PostgreSQL

book

Article ID: 325926

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
Upon logging into the vRealize Orchestrator client, you are unable to see any workflow content.

In some environments, you may be able to log into https://<vra_appliance>:8283/vco-controlcenter/?advanced and access the database settings page. On this page, you see the database type set to something other than PostgreSQL.

Server.log may include errors similar to: [JdbcLicenseWarden] Unable to get license elements for query
ControlCenter.log may include errors similar to: unable to start the DerbyDB or another database type.

Environment

VMware vRealize Automation 7.3.x

Resolution

To restore the default embedded vRealize Orchestrator database settings on a vRealize Automation 7.3.x appliance, please complete the steps below:
  1. Backup and/or snapshot the vRealize Automation environment.
  2. Secure Shell (SSH) login to each vRealize Automation virtual appliance node.
  3. Stop the vRealize Orchestrator services:
    • service vco-server stop
    • service vco-configurator stop
  4.  Reset the vRealize Orchestrator database configuration by running the following command
    • /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh db --type psql --skipUpdateDbScheme --databaseName vcac --dbUsername vcac --dbPassword $(/usr/sbin/vcac-config prop-util -d --p `xpath /etc/vcac/server.xml "//@password" 2>&1 | grep password | cut -d'"' -f2`) --port 5433 --jdbcUrl 'jdbc:postgresql://127.0.0.1:5433/vcac?sslmode=verify-ca&sslrootcert=/var/vmware/vpostgres/current/.postgresql/root.crt' --host 127.0.0.1
  5. Start the vRealize Orchestrator services:
    • service vco-server start
    • service vco-configurator start
  6. Login to the vRealize Orchestrator client and validate the most recent content is still present.

Note: The first vco-server start, after resetting the database connection, may take a bit more time as changing the database settings will force plug-in reinstalls (This is a safe procedure).