System information

ManualsBrandsRed Hat ManualsConsumer electronicsCERTIFICATE 7.3 RELEASE NOTES

Welcome to Greenplum Database 4.2.7.3 1

Rev: A01

Updated: May 15, 2014

Welcome to Greenplum Database 4.2.7.3

Greenplum Database is a massively parallel processing (MPP) database server that

supports next generation data warehousing and large-scale analytics processing. By

automatically partitioning data and running parallel queries, it allows a cluster of

servers to operate as a single database supercomputer performing tens or hundreds

times faster than a traditional database. It supports SQL, MapReduce parallel

processing, and data volumes ranging from hundreds of gigabytes, to hundreds of

terabytes.

Note: This document contains pertinent release information about Greenplum

Database 4.2.7.3. For previous versions of the release notes for Greenplum Database,

go to Support Zone.

About Pivotal, Inc.

Greenplum is currently transitioning to a new corporate identity (Pivotal Software,

Inc.). During this transition, there will be some legacy instances of our former

corporate identity (Greenplum) appearing in our products and documentation. If you

have any questions or concerns, please do not hesitate to contact us through our web

site:

http://www.gopivotal.com/contact

About Greenplum Database 4.2.7.3

Greenplum Database 4.2.7.3 is a maintenance that contains a critical fix. Please refer

to the following sections for more information about this release.

• Downloading Greenplum Database

• Changed Feature

• Supported Platforms

• Resolved Issues in Greenplum Database 4.2.7.3

• Known Issues in Greenplum Database 4.2.7.3

• Upgrading to Greenplum Database 4.2.x.x

• Greenplum Database Tools Compatibility

• Greenplum Database Extensions Compatibility

• Hadoop Distribution Compatibility

• Greenplum Database 4.2 Documentation

Summary of content (26 pages)

PAGE 1
Rev: A01 Updated: May 15, 2014 Welcome to Greenplum Database 4.2.7.3 Greenplum Database is a massively parallel processing (MPP) database server that supports next generation data warehousing and large-scale analytics processing. By automatically partitioning data and running parallel queries, it allows a cluster of servers to operate as a single database supercomputer performing tens or hundreds times faster than a traditional database.
PAGE 2
Greenplum Database 4.2.7.3 Release Notes Downloading Greenplum Database The Greenplum Database software and documentation can be accessed from the following locations: • Greenplum Database 4.2.7.3 server software, and other Greenplum Database 4.2.7.3 software including tools and extension packages, can be downloaded from the EMC Download Center. • Documentation for Greenplum Database 4.2.7.3 is available from the Pivotal Documentation site.
PAGE 3
Greenplum Database 4.2.7.3 Release Notes Resolved Issues in Greenplum Database 4.2.7.3 The table below lists issues that are now resolved in Greenplum Database 4.2.7.3. For issues resolved in prior releases, refer to the corresponding release notes available from Support Zone. Table 1 Resolved Issues in 4.2.7.3 Issue Number Category Resolved in Description 22787 Monitoring: gpperfmon server 4.2.7.3 In some cases, the Greenplum Database gpmmon process failed.
PAGE 4
Greenplum Database 4.2.7.3 Release Notes Table 1 Resolved Issues in 4.2.7.3 Issue Number Category Resolved in Description 22060 Functions and Languages, Resource Management 4.2.7.1 The string_to_array function fails to produce an array when the input string is larger than 250MB. 22045 Dispatch 4.2.7.1 Reporting errors when the maximum number of connections on Greenplum Database segment instances were exceeded has been enhanced.
PAGE 5
Greenplum Database 4.2.7.3 Release Notes Table 1 Resolved Issues in 4.2.7.3 Issue Number Category Resolved in Description 20466 Catalog and Metadata 4.2.7.1 If a constraint is created with the same name as an existing constraint, the only way to remove the second constraint was to drop all constraints. The fix is to not allow duplicate constraint names. While creating a new table or alter table for new constraint creation, duplicate constraint name are not allowed. 19965 Query Execution 4.2.7.
PAGE 6
Greenplum Database 4.2.7.3 Release Notes Table 1 Resolved Issues in 4.2.7.3 Issue Number Category Resolved in Description 18623 DDL and Utility Statements 4.2.7 When an out-of-memory condition occurred during a hash table expansion, the hash entry that was being created could have been in an incomplete state. This resulted in misbehavior in the cleanup code. 18576 Transaction Management 4.2.
PAGE 7
Greenplum Database 4.2.7.3 Release Notes Known Issues in Greenplum Database 4.2.7.3 This section lists the known issues in Greenplum Database 4.2.7.3. A workaround is provided where applicable. For known issues discovered in previous releases, including patch releases to Greenplum Database 4.1 or 4.0.x, see the corresponding release notes, available from Support Zone: Table 2 All Known Issues in 4.2.7.
PAGE 8
Greenplum Database 4.2.7.3 Release Notes Table 2 All Known Issues in 4.2.7.3 Issue Category Description 20822 Backup and Restore Special characters such as !, $, #, and @ cannot be used in the password for the Data Domain Boost user when specifying the Data Domain Boost credentials with the gpcrondump options --ddboost-host and --ddboost-user. 18247 DDL and Utility Statements TRUNCATE command does not remove rows from a sub-table of a partitioned table.
PAGE 9
Greenplum Database 4.2.7.3 Release Notes Table 2 All Known Issues in 4.2.7.3 Issue Category Description 18850 Backup and Restore Data Domain Boost credentials cannot be set up in some environments due to the absence of certain libraries (for example, libstdc++) expected to reside on the platform. Workaround: Install the missing libraries manually on the system.
PAGE 10
Greenplum Database 4.2.7.3 Release Notes Table 2 All Known Issues in 4.2.7.3 Issue Category Description 17513 Management Scripts Suite Running more than one gpfilespace command concurrently with itself to move either temporary files (--movetempfilespace) or transaction files (--movetransfilespace) to a new filespace can in some circumstances cause OID inconsistencies. Workaround: Do not run more than one gpfilespace command concurrently with itself.
PAGE 11
Greenplum Database 4.2.7.3 Release Notes Table 2 All Known Issues in 4.2.7.3 Issue Category Description 16519 Backup and Restore Limited data restore functionality and/or restore performance issues can occur when restoring tables from a full database backup where the default backup directory was not used. In order to restore from backup files not located in the default directory you can use the -R to point to another host and directory.
PAGE 12
Greenplum Database 4.2.7.3 Release Notes Table 2 All Known Issues in 4.2.7.3 Issue Category Description 16064 Backup and Restore Restoring a compressed dump with the --ddboost option displays incorrect dump parameter information. When using gpdbrestore --ddboost to restore a compressed dump, the restore parameters incorrectly show “Restore compressed dump = Off”. This error occurs even if gpdbrestore passes the --gp-c option to use gunzip for in-line de-compression.
PAGE 13
Greenplum Database 4.2.7.3 Release Notes Upgrading to Greenplum Database 4.2.x.x The upgrade path supported for this release is Greenplum Database 4.1.x.x to Greenplum Database 4.2.x.x. The minimum recommended upgrade path for this release is from Greenplum Database version 4.1.1.5. If you have an earlier major version of the database, you must first upgrade to version 4.1.x. For detailed upgrade procedures and information, see the following sections: • Upgrading from 4.2.x.x to 4.2.7.
PAGE 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.
PAGE 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.
PAGE 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.
PAGE 17
Greenplum Database 4.2.7.3 Release Notes 10. (optional but strongly recommended) Back up all databases in your Greenplum Database system using gpcrondump (or zfs snapshots on Solaris systems). See the Greenplum Database Administrator Guide for more information on how to do backups using gpcrondump. Make sure to secure your backup files in a location outside of your Greenplum data directories. 11.
PAGE 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.
PAGE 19
Greenplum Database 4.2.7.3 Release Notes Upgrade Checklist This checklist provides a quick overview of all the steps required for an upgrade from 4.1.x.x to 4.2.x.x. Detailed upgrade instructions are provided in the Upgrade Procedure section. Pre-Upgrade Preparation (on your current system) * 4.1.x.x system is up and available Log in to your master host as the gpadmin user (your Greenplum superuser).
PAGE 20
Greenplum Database 4.2.7.3 Release Notes Upgrade gpfdist on all of your ETL hosts. Rebuild any custom modules against your 4.2.x.x installation. Download and install any Greenplum Database extensions. (Optional) Install the latest Command Center Console and update your environment to point to the latest Command Center binaries. Inform all database users of the completed upgrade. For Users Running Greenplum Database 4.0.x.x Users on a release prior to 4.1.x.x cannot upgrade directly to 4.2.x.x.
PAGE 21
Greenplum Database 4.2.7.3 Release Notes Troubleshooting a Failed Upgrade If you experience issues during the migration process, go to the Support page at Support Zone or contact Greenplum customer support at one of the following numbers: United States: 800-782-4362 (1-800-SVC-4EMC) Canada: 800-543-4782 Worldwide: +1-508-497-7901 Be prepared to provide the following information: • A completed Upgrade Procedure.
PAGE 22
Greenplum Database 4.2.7.
PAGE 23
Greenplum Database 4.2.7.3 Release Notes Table 4 Greenplum Database Extensions Compatibility Extension Components Greenplum Database Extension Name Version PostGIS 2.0.3 Proj 4.8.0 Geos 3.3.8 PostGIS 1.4.2 Proj 4.7.0 Geos 3.2.2 PL/Java Based on 1.4.0 Java JDK 1.6.0_26 Update 31 PL/R 8.3.0.12 R 2.13.0 PL/Perl Based on PostgreSQL 9.1 Perl 5.12.4 on RHEL 6.x 5.5.8 on RHEL 5.x, SUSE 10 PL/Perl Based on PostgreSQL 9.1 Perl 5.12.4 on RHEL 5.x, SUSE 10 PL/Perl Based on PostgreSQL 9.
PAGE 24
Greenplum Database 4.2.7.3 Release Notes Hadoop Distribution Compatibility Use the gppkg utility to install the gNet package containing the jar file for the extensions, the libraries, and the documentation for the gphdfs extensions. To install the correct distribution, refer to the following Hadoop extensions compatibility matrix: Table 5 Hadoop Extensions Compatibility Hadoop Distribution Version Pivotal HD Pivotal HD 1.01 Greenplum HD Greenplum HD 1.1 Greenplum HD 1.2 Cloudera cdh3u2 cdh3u4 CDH4.
PAGE 25
Greenplum Database 4.2.7.3 Release Notes Greenplum Database 4.2 Documentation For the latest Greenplum Database documentation go to Pivotal Documentation. Greenplum documentation is provided in PDF format. Table 6 Greenplum Database Documentation Title Revision Greenplum Database 4.2.7.3 Release Notes A01 Greenplum Database 4.2 Installation Guide A11 Greenplum Database 4.2 Database Administrator Guide A08 Greenplum Database 4.2 System Administrator Guide A12 Greenplum Database 4.
PAGE 26
Greenplum Database 4.2.7.3 Release Notes Copyright © 2014 Pivotal Software, Inc. All rights reserved. Pivotal Software, Inc. believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." PIVOTAL SOFTWARE, INC.