System information
Known Issues in Greenplum Database 4.2.7.3 8
Greenplum Database 4.2.7.3 Release Notes
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. 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.
19788 Replication:
Resync,
Transaction
Management
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
gprecoverseg
.
19772 Interconnect 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.
19705 Loaders: gpload
gpload
fails on Windows XP with Python 2.6.
Workaround: Install Python 2.5 on the system where gpload is installed.
19493
19464
19426
Backup and
Restore
The
gpcrondump
and
gpdbrestore
utilities do not handle errors returned by DD
Boost or Data Domain correctly.
These are two examples:
• If invalid Data Domain credentials are specified when setting the Data Domain
Boost credentials with the
gpcrondump
utility, the error message does not
indicate that invalid credentials were specified.
• Restoring a Greenplum database from a Data Domain system with
gpdbrestore
and the
--ddboost
option indicates success even though segment failures
occured during the restore.
Workaround: The errors are logged in the master and segment server backup or
restore status and report files. Scan the status and report files to check for error
messages.
19278 Backup and
Restore
When performing a selective restore of a partitioned table from a full backup
with
gpdbrestore
, the data from leaf partitions are not restored.
Workaround: When doing a selective restore from a full backup, specify the
individual leaf partitions of the partitioned tables that are being restored.
Alternatively, perform a full backup, not a selective backup.
15692
17192
Backup and
Restore
Greenplum Database’s implementation of RSA lock box for Data Domain
Boost changes backup and restore requirements for customers running
SUSE.
The current implementation of the RSA lock box for Data Domain Boost login
credential encryption only supports customers running on Red Hat Enterprise
Linux.
Workaround: If you run Greenplum Database on SUSE, use NFS as your backup
solution. See the Greenplum Database System Administrator Guide
for information
on setting up a NFS backup.
Table 2
All Known Issues in 4.2.7.3
Issue Category Description