System information

Known Issues in Greenplum Database 4.2.7.3 9
Greenplum Database 4.2.7.3 Release Notes
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.
18851 Backup and
Restore
When performing a data-only restore of a particular table, it is possible to introduce
data into Greenplum Database that contradicts the distribution policy of that table.
In such cases, subsequent queries may return unexpected and incorrect results. To
avoid this scenario, we suggest you carefully consider the table schema when
performing a restore.
18774 Loaders External web tables that use IPv6 addresses must include a port number.
18713 Catalog and
Metadata
Drop language plpgsql cascade results in a loss of
gp_toolkit functionality.
Workaround: Reinstall
gp_toolkit .
18710 Management
Scripts Suite
Greenplum Management utilities cannot parse IPv6 IP addresses.
Workaround: Always specify IPv6 hostnames rather than IP addresses
18703 Loaders 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.
12468 Management
Scripts Suite
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,
18785 Loaders 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.
18414 Loaders Unable to define external tables with fixed width format and empty line delimiter
when file size is larger than gpfdist chunk (by default, 32K).
14640 Backup and
Restore
gpdbrestore outputting incorrect non-zero error message.
When performing single table restore,
gpdbrestore gives warning messages about
non-zero tables however prints out zero rows.
17285 Backup and
Restore
NFS backup with
gpcrondump -c can fail.
In circumstances where you haven't backed up to a local disk before, backups to
NFS using
gpcrondump with the -c option can fail. On fresh systems where a
backup has not been previously invoked there are no dump files to cleanup and the
-c flag will have no effect.
Workaround: Do not run
gpcrondump with the -c option the first time a backup is
invoked from a system.
17837 Upgrade/
Downgrade
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:
$GPHOME/share/postgresql/gp_toolkit.sql .
Table 2 All Known Issues in 4.2.7.3
Issue Category Description