System information

Upgrading to Greenplum Database 4.2.x.x 16
Greenplum Database 4.2.7.3 Release Notes
5. If you have failed segments, you must recover them using gprecoverseg before
you can upgrade.
$ gprecoverseg
Note: It might be necessary to restart the database if the preferred role does not
match the current role; for example, if a primary segment is acting as a mirror
segment or a mirror segment is acting as a primary segment.
6. Copy or preserve any additional folders or files (such as backup folders) that you
have added in the Greenplum data directories or
$GPHOME directory. Only files or
folders strictly related to Greenplum Database operations are preserved by the
migration utility.
Install the Greenplum Software Binaries
1. Download or copy the installer file to the Greenplum Database master host.
2. Unzip the installer file. For example:
# unzip greenplum-db-4.2.x.x- PLATFORM .zip
3. Launch the installer using bash . For example:
# /bin/bash greenplum-db-4.2.x.x- PLATFORM .bin
4. The installer will prompt you to accept the Greenplum Database license
agreement. Type
yes to accept the license agreement.
5. The installer will prompt you to provide an installation path. Press ENTER to
accept the default install path (for example:
/usr/local/greenplum-db-4.2.x.x), or enter an absolute path to an install
location. You must have write permissions to the location you specify.
6. The installer will install the Greenplum software and create a greenplum-db
symbolic link one directory level above your version-specific Greenplum
installation directory. The symbolic link is used to facilitate patch maintenance
and upgrades between versions. The installed location is referred to as
$GPHOME .
7. Source the path file from your new 4.2.x.x installation. For example:
$ source /usr/local/greenplum-db-4.2.x.x/ greenplum_path.sh
8. Run the gpseginstall utility to install the 4.2.3.x binaries on all the segment
hosts specified in the
hostfile . For example:
$ gpseginstall -f hostfile
Upgrade Execution
During upgrade, all client connections to the master will be locked out. Inform all
database users of the upgrade and lockout time frame. From this point onward, users
should not be allowed on the system until the upgrade is complete.
9. Source the path file from your old 4.1.x.x installation. For example:
$ source /usr/local/greenplum-db-4.1.1.5/ greenplum_path.sh