7.1

8 Run the following command to format the new swap partition.
mkswap /dev/sda2
9 Run the following command to mount the swap partition.
swapon -a
10 Reboot the vRealize Automation appliance.
11 After the appliance reboots, run the following command to resize the Disk 1 partition table.
resize2fs /dev/sda1
12 To verify that the disk expansion is successful, run df -h and check that the available disk space
on /dev/sda1 is greater than 3 GB.
Manual PostgreSQL Database Merge
The external PostgreSQL database merge with the embedded PostgreSQL database does not succeed.
Problem
If the PostgreSQL database upgrade merge does not succeed, you can perform a manual merge.
Solution
1 Revert the vRealize Automation virtual appliance to the snapshot you made before upgrade.
2 Log in to the vRealize Automation virtual appliance and run this command to allow upgrade to
complete if the database merge does not succeed.
touch /tmp/allow-external-db
The command does not disable auto merge.
3 On the remote PostgreSQL database host, connect to the PostgreSQL database using the psql tool and
run these commands.
CREATE EXTENSION IF NOT EXISTS "hstore";
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
CREATE SCHEMA saas AUTHORIZATION vcac;
The user in this command is vcac. If vRealize Automation connects to the external database with a
dierent user, replace vcac in this command with the name of that user.
CREATE EXTENSION IF NOT EXISTS "citext" SCHEMA saas;
4 Run upgrade.
If upgrade is successful, the system works as expected with the external PostgreSQL database. Ensure
that the external PostgreSQL database is running properly.
5 Log in to the vRealize Automation virtual appliance and run these commands
/etc/bootstrap/postupdate.d/00-20-db-merge-external
/etc/bootstrap/postupdate.d/11-db-merge-external
Chapter 8 Troubleshooting the Upgrade
VMware, Inc. 43