System information
Upgrading to Greenplum Database 4.2.x.x 18
Greenplum Database 4.2.7.3 Release Notes
Note: If the migration does not complete successfully, contact Customer Support
(see
“Troubleshooting a Failed Upgrade” on page 21).
17. The migration can take a while to complete. After the migration utility has
completed successfully, the Greenplum Database 4.2.x.x system will be running
and accepting connections.
Note: After the migration utility has completed, the resynchronization of the
mirror segments with the primary segments continues. Even though the system is
running, the mirrors are not active until the resynchronization is complete.
Post-Upgrade (on your 4.2.x.x system)
18. If your system had a standby master host configured, reinitialize your standby
master using
gpinitstandby
:
$ gpinitstandby -s
standby_hostname
19. If your system uses external tables with
gpfdist
, stop all
gpfdist
processes on
your ETL servers and reinstall
gpfdist
using the compatible Greenplum
Database 4.2.x.x Load Tools package. Application Packages are available from
the
EMC Download Center.
20. Rebuild any custom modules against your 4.2.x.x installation (for example, any
shared library files for user-defined functions in
$GPHOME/lib
).
21. Greenplum Database 4.2.x.x introduced the
gppkg
utility to install Greenplum
Database extensions. If you were previously using any PostgreSQL extensions
such as pgcrypto, PL/R, PL/Java, PL/Perl, and PostGIS, download the
corresponding packages from the
EMC Download Center, and install using this
new utility. See the Greenplum Database Administrator Guide 4.2 or later for
usage details.
22. If you want to utilize the Greenplum Command Center management tool, install
the latest Command Center Console and update your environment variable to
point to the latest Command Center binaries (source the
gpperfmon_path.sh
file
from your new installation).
Note that the Greenplum Command Center management tool replaces Greenplum
Performance Monitor.
Command Center Console packages are available from the EMC Download
Center or Pivotal Network.
23. Inform all database users of the completed upgrade. Tell users to update their
environment to source the Greenplum Database 4.2.x.x installation (if necessary).