Use this procedure to migrate an Open Source Greenplum Database installation to commercial VMware Greenplum.
This process replaces the application and software but does not migrate any data.
If you have configured the Greenplum Platform Extension Framework (PXF) in your previous Greenplum Database installation, you must stop the PXF service, and you must back up PXF configuration files before upgrading to a new version of Greenplum Database. See PXF Pre-Upgrade Actions for instructions.
Review the Greenplum Database Platform Requirements topic to verify that you have all the software you need in place to successfully migrate to VMware Greenplum.
Migrating from Open Source Greenplum Database to commercial VMware Greenplum involves stopping the open source Greenplum Database, replacing the Greenplum Database software, and restarting the database. If your open source Greenplum Database installation includes optional extension packages, you must reinstall them at the end of this procedure.
Follow these steps to migrate Open Source Greenplum Database to VMware Greenplum:
Log into your Open Source Greenplum Database coordinator host as the Greenplum administrative user:
$ su - gpadmin
Terminate any active connections to the database, and then perform a smart shutdown of your Greenplum Database 6.x system. This example uses the
-a option to deactivate confirmation prompts:
$ gpstop -a
Download the VMware Greenplum package from VMware Tanzu Network, and then copy it to the
gpadmin user's home directory on each coordinator, standby, and segment host.
If you used
apt to install Greenplum Database to the default location, run the following commands on each host to replace the software:
For RHEL/CentOS systems:
$ sudo yum install ./greenplum-db-<version>-<platform>.rpm
For Ubuntu systems:
# sudo apt install ./greenplum-db-<version>-<platform>.deb
apt command installs commercial VMware Greenplum software files into a version-specific directory under
/usr/local and updates the symbolic link
/usr/local/greenplum-db to point to the new installation directory.
If you used
rpm to install Open Source Greenplum Database to a non-default location on RHEL/CentOS systems, run
rpm on each host to replace the software and specify the same custom installation directory with the
--prefix option, as in the following example:
$ sudo rpm -U ./greenplum-db-<version>-<platform>.rpm --prefix=<directory>
rpm command installs the new Greenplum Database software files into a version-specific directory under the directory you specify, and updates the symbolic link
Update the permissions for the new installation. For example, run the following command as root to change the user and group of the installed files to
$ sudo chown -R gpadmin:gpadmin /usr/local/greenplum*
If, during this process, you are replacing the open source Greenplum Databse software with a newer version of VMware Greenplum software, edit the environment of the Greenplum Database superuser (
gpadmin) and verify that you are sourcing the
greenplum_path.sh file for the new installation. For example, update the following line in the
.bashrc file or in your profile file:
If you are sourcing a symbolic link (
/usr/local/greenplum-db) in your profile files, the symbolic link will redirect to the newly installed gpdb folder; no action is necessary.
Source the environment file you just edited. For example:
$ source ~/.bashrc
Once all segment hosts have been updated, log into the Greenplum Database coordinator as the
gpadmin user and restart your Greenplum Database system:
$ su - gpadmin $ gpstart
Check the database version:
$ su - gpadmin $ psql -d postgres $ select versions();
The output version string should no longer include "open source".
Reinstall any Greenplum Database extensions that you used with the earlier Open Source Greenplum Database installation.