Pivotal Knowledge Base

Follow

gpdbrestore Fails with the Message "No dumped tables to restore" for the Child Partition Table"

Environment

Pivotal Greenplum Database (GPDB) 4.3.x

Symptom

When attempting to restore a child partition to a different location of schema backed up from a gpcrondump where the parent partition was not backed up, it fails.

Error Message:

20180207:14:10:23:564896 gpdbrestore:mdw:gpadmin-[INFO]:-Starting gpdbrestore with args: -a --change-schema restore -t 20180207131210 --ddboost --table-file=/tmp/part_bkp_restore_test.txt 
20180207:14:11:09:564896 gpdbrestore:mdw:gpadmin-[CRITICAL]:-gpdbrestore failed. (Reason='No dumped tables to restore.') exiting...

Cause 

This is functioning as designed. When doing a backup of just a child partition without the parent partition, the DDL for the table is not retrieved and the restore will fail with the error above.

Resolution

If it's a business requirement to restore a child partition only, you can do the following:

Backup the parent partition, this will back up the child partition required to restore. Restore the child partition with gpdbrestore. This will work as the ddl of the table will be backed up with the parent gpcrondump.

 

Comments

Powered by Zendesk