System information

Upgrading to Greenplum Database 4.2.x.x 15
Greenplum Database 4.2.7.3 Release Notes
• Regular CHECK , PRIMARY KEY , or UNIQUE constraints added by database users
usually appear on every sub-table of the partitioned table. Their names may need
to be adjusted. If necessary,
gpmigrator creates a repair script to do this.
• PRIMARY KEY and UNIQUE constraints on partitioned tables that do not include all
the columns of the partition key need to be removed. If needed,
gpmigrator
creates a repair script to do this. Note that the unique index underlying the
constraint remains and provides the same protection against duplicate keys as did
the constraint. As was previously the case, it is possible for different parts of the
partitioned table to contain the same key value.
• If the added constraints appear on some but not all of the sub-tables that make up
a partitioned table, they cannot be updated automatically. In this case, you need to
either drop the irregular constraints or add the missing constraints. Other causes of
irregularity may exist but are rare. Greenplum recommends that you contact
support if you encounter any issues with partitioned tables that cannot be resolved
automatically with
gpmigrator .
Upgrade Procedure
This section divides the upgrade into the following phases: pre-upgrade preparation,
software installation, upgrade execution, and post-upgrade tasks.
We have also provided you with an Upgrade Checklist that summarizes this
procedure.
Important: Carefully evaluate each section and perform all required and conditional
steps. Failing to perform any of these steps can result in an aborted upgrade,
placing your system in an unusable or even unrecoverable state.
Pre-Upgrade Preparation (on your 4.1.x system)
Perform these steps on your current 4.1.x Greenplum Database system. This
procedure is performed from your Greenplum master host and should be executed by
the Greenplum superuser (
gpadmin ).
1. Log in to the Greenplum Database master as the gpadmin user:
$ su - gpadmin
2. (optional) Vacuum all databases prior to upgrade. For example:
$ vacuumdb database_name
3. (optional) Clean out old server log files from your master and segment data
directories. For example, to remove log files from 2011 from your segment hosts:
$ gpssh -f seg_host_file -e 'rm
/gpdata/*/gp*/pg_log/gpdb-2011-*.csv'
Note: Running Vacuum and cleaning out old logs files is not required, but it will
reduce the size of Greenplum Database files to be backed up and migrated.
4. Run gpstate to check for failed segments.
$ gpstate