System information

Upgrading to Greenplum Database 4.2.x.x 14
Greenplum Database 4.2.7.3 Release Notes
6. Run the gpseginstall utility to install the 4.2.7.3 binaries on all the segment
hosts specified in the
hostfile . For example:
$ gpseginstall -f hostfile
7. After all segment hosts have been upgraded, you can log in as the gpadmin user
and restart your Greenplum Database system:
$ su - gpadmin
$ gpstart
8. If you are utilizing Data Domain Boost, you have to re-enter your DD Boost
credentials after upgrading from Greenplum Database 4.2.1 to 4.2.7.3 as follows:
gpcrondump --ddboost-host ddboost_hostname --ddboost-user
ddboost_user
Note that if you do not reenter your login credentials after an upgrade, your
backup will never start because the Greenplum Database cannot connect to the
Data Domain system. You will receive an error advising you to check your login
credentials.
Upgrading from 4.1.x.x to 4.2.x.x
This section describes how you can upgrade from Greenplum Database 4.1.x.x or later
to Greenplum Database 4.2.x.x. For users running versions prior to 4.1.x.x of
Greenplum Database, see the following:
• For Users Running Greenplum Database 4.0.x.x
• For Users Running Greenplum Database 3.3.x.x
Planning Your Upgrade
Before you begin your upgrade, make sure the master and all segments (data
directories and filespace) have at least 2GB of free space.
Prior to upgrading your database, Greenplum recommends that you run a pre-upgrade
check to verify your database is healthy.
You can perform a pre-upgrade check by executing the gpmigrator ( _mirror ) utility
with the
--check-only option.
For example:
source $new_gphome/greenplum_path.sh;
gpmigrator_mirror --check-only $old_gphome $new_gphome
Note: Performing a pre-upgrade check of your database with the gpmigrator
( _mirror ) utility should done during a database maintenance period. When the utility
checks the database catalog, users cannot access the database.
Some of the rules for partitioned tables are different in 4.2 than in previous releases.
gpmigrator detects partitioned tables that violate these new rules and aborts the
upgrade. In most cases,
gpmigrator will create a repair script you can run to bring
your 4.1 Greenplum Database into line with the new rules in 4.2. See
Upgrading
Partitioned Tables with Constraints for more details.
Upgrading Partitioned Tables with Constraints
Partition tables with CHECK , PRIMARY KEY , or UNIQUE constraints must be updated
prior to upgrading: