Known Issues in Greenplum Database

Greenplum Database V3.0 Known Issues

There are 46 known issues in Greenplum Database Version 3.0. There is 1 issue reported to be resolved in 3.0.

1. Known Issues in Greenplum Database Related to Backup and Restore (15 issues)
(Issues: 21838,20822,19493,19464,19426,19278,15692,17192,18850,18851,14640,17285,16519,16064,15899)

(Issues: 20453,21724)

(Issues: 19772)

(Issues: 19705,18774,18703,18785,18414,17189)

(Issues: 16067,16267,15954,16269,16278,17113,17334,17795,17513,12468,18710,16129)

(Issues: 18713)

(Issues: 17837 )

(Issues: 17780,18247,21129 )

(Issues: 17604 )

(Issues: 17415)

(Issues: 17221 )

Known issues in Greenplum Database related to Greenplum Database Replication(Segment Mirroring, Resync, Transaction Management)

posted Jan 25, 2014, 9:06 AM by Sachchida Ojha

1. Issue 21917
In some rare cases after the Greenplum Database utility gprecoverseg was run, some append-optimized tables and a persistent table were detected having less data on a mirror segment corresponding to a primary segment.

2. Issue 19788
In some rare circumstances, performing a full recovery with gprecoverseg  
fails due to inconsistent LSN.
Workaround: Stop and restart the database. Then perform a full recovery with 

Known issues in Greenplum Database related to Greenplum Database Resource Management

posted Jan 25, 2014, 9:02 AM by Sachchida Ojha

Issue 17221
Resource queue deadlocks may be encountered if a cursor is associated with a query invoking a function within another function.

Known issues in Greenplum Database related to Greenplum Database Installer

posted Jan 25, 2014, 9:00 AM by Sachchida Ojha

1. Issue 17415
When you run gppkg -q -info<some gppkg>, the system shows the GPDBversion as main build dev.

Known issues in Greenplum Database related to Greenplum Database Security

posted Jan 25, 2014, 8:58 AM by Sachchida Ojha

1. Issue 17604
A Red Hat Enterprise Linux (RHEL) 6.x security configuration file limits the number of processes that can run on gpadmin.
RHEL 6.x contains a security file (/etc/security/limits.d/90-nproc.conf) that limits available processes running on gpadmin to 1064.
Workaround: Remove this file or increase the processes to 131072.

Known issues in Greenplum Database related to Greenplum DDL/DML( Partitioning) and Utility Statements

posted Jan 25, 2014, 8:55 AM by Sachchida Ojha

1. Issue 17780
ALTER TABLE ADD PARTITION inheritance issue. When performing an ALTER TABLE ADD PARTITION operation, the resulting parts may not correctly inherit the storage properties of the parent table in cases such as adding a default partition or more complex subpartitioning. This issue can be avoided by explicitly dictating the storage properties during the ADD PARTITION invocation. For leaf partitions that are already afflicted, the issue can be rectified through use of EXCHANGE PARTITION.

2. Issue 18247
TRUNCATE command does not remove rows from a sub-table of a partitioned 
table. If you specify a sub-table of a partitioned table with the TRUNCATE
command, the command does not remove rows from the sub-table and its 
child tables.
Workaround: Use the ALTER TABLE command with the TRUNCATE PARTITION clause to remove rows from the sub-table and its child tables.

3. Issue 21129
SSL is only supported on the master host. It is not supported on segment 

Known issues in Greenplum Database related to Greenplum Upgrade/Downgrade

posted Jan 25, 2014, 8:51 AM by Sachchida Ojha

1. Issue 17837
Major version upgrades internally depend on the gp_toolkit system schema. The alteration or absence of this schema may cause upgrades to error out during
preliminary checks.
Workaround: To enable the upgrade process to proceed, you need to reinstall the gp_toolkit schema in all affected databases by applying the SQL file found here:

Known issues in Greenplum Database related to Greenplum Database Catalog and Metadata

posted Jan 25, 2014, 8:49 AM by Sachchida Ojha

1. Issue 18713
Drop language plpgsql cascade results in a loss of gp_toolkit functionality.
Workaround: Reinstall gp_toolkit.

Known issues in Greenplum Database related to Greenplum Management Scripts Suite

posted Jan 25, 2014, 8:40 AM by Sachchida Ojha

1. Issue 16067
gpkill does not validate the user input for password_hash_algorithm.  The current behavior shows a success message for any input value. However, the
server configuration parameter value is not updated if the input is invalid. When the user tries to set the value for a session from within psql, it fails with the appropriate
error message.

2. Issue 16267, 15954
gpkill cannot kill processes that are deemed STUCK.
Workaround: Kill the STUCK processes using OS kill.

3. Issue 16269
gpkill should attempt to kill each given pid. gpkill accepts the list of pids but only shows that one of the processes may not be

4. Issue 16278
gpkill shows that it failed to kill the gpload process, but in fact the process was successfully aborted with all the data loaded correctly.

5. Issue 17113
Filespaces are inconsistent when the Greenplum database is down. Filespaces become inconsistent in case of a network failure. Greenplum
recommends that processes such as moving a filespace be done in an environment with an uninterrupted power supply

6. Issue 17334
You may see warning messages that interfere with the operation of management scripts when logging in. Greenplum recommends that you edit the /etc/motd file and add the warning message to it. This will send the messages to are redirected to stdout and not stderr. You must encode these warning messages in UTF-8 format.

7. Issue 17795
Under some circumstances, gppkg on SUSE is unable to correctly interpret error messages returned by rpm. On SUSE, gppkg is unable to operate correctly under circumstances that require a non-trivial interpretation of underlying rpm commands. This includes scenarios that result from overlapping packages, partial installs, and partial uninstalls.

8. Issue 17513
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. If an OID inconsistency is introduced gpfilespace --movetempfilespace or 
gpfilespace --movetransfilespace can be used to revert to the default

9. Issue 12468
gpexpand --rollback fails if an error occurs during expansion such that it leaves the database down.
gpstart also fails as it detects that expansion is in progress and suggests to run gpexpand --rollback which will not work because the database is down.
Workaround: Run gpstart -m to start the master and then run rollback,

10. Issue 18710
Greenplum Management utilities cannot parse IPv6 IP addresses.
Workaround: Always specify IPv6 hostnames rather than IP addresses

11. Issue 16129
gpkill does not run on the Solaris platform. The gpkill utility is using an internal tool called “glider” to introspect processes and glean/archive some relevant information before actually killing processes. In some cases, our invocation of this tool fails to yield the desired introspective information.

Known issues in Greenplum Database related to Greenplum loader (gpload, gpfdist)

posted Jan 25, 2014, 8:28 AM by Sachchida Ojha   [ updated Nov 4, 2014, 9:04 AM ]

1. Issue 19705
gpload fails on Windows XP with Python 2.6. 
Workaround: Install Python 2.5 on the system where gpload is installed.
The gadget spec URL could not be found
2. Issue 18774
External web tables that use IPv6 addresses must include a port number.

3. Issue 18703
The bytenum field (byte offset in the load file where the error occurred) in the error log when using gpfdist with data in text format errors is not populated, making it
difficult to find the location of an error in the source file.

4. Issue 18785
Running gpload with the --ssl option and the relative path of the source file results in an error that states the source file is missing.
Workaround: Provide the full path in the yaml file or add the loaded data file to the certificate folder.

5. Issue 18414
Unable to define external tables with fixed width format and empty line delimiter when file size is larger than gpfdist chunk (by default, 32K).
The gadget spec URL could not be found
6. Issue 17189
gpfdist shows the error “Address already in use” after successfully binding to socket IPv6. Greenplum supports IPv4 and IPv6. However, gpfdist fails to bind to socket IPv4, and shows the message “Address already in use”, but binds successfully to socket IPv6.

Known issues in Greenplum Database related to Interconnect

posted Jan 25, 2014, 8:20 AM by Sachchida Ojha

1. Issue 19772
After installing Greenplum Database 4.2.4, downgrading the Greenplum Database installation to a previous minor version causes a crash. 
Workaround: Before downgrading Greenplum Database 4.2.4 to a previous minor version, change the value for the Greenplum Database parameter gp_interconnect_type from UDPIFC to a supported value such as UDP. The parameter value UDPIFC was introduced in Greenplum Database 4.2.4 and is not
valid in previous versions.

1-10 of 12