gpcopy: error "unrecognized configuration parameter lock_timeout"

Products

• VMware Tanzu Greenplum
• VMware Tanzu Greenplum / Gemfire
• VMware Tanzu Data Suite
• VMware Tanzu Data Suite

Issue/Introduction

Running gpcopy from 6.x to 5.x fails with the following error:

pq: unrecognized configuration parameter "lock_timeout"

This type of error can occur when copying tables from a higher major version of Greenplum to a lower major version, for example from 6.x to 5.x

Example:

[gpadmin@mydb-m]$ ./gpcopy --skip-existing --dest-host 'mydb-m' --dest-port '3002' --include-table 'gpadmin.public.test' --source-host 'mydb-m' --source-port '3000' 
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Set to no compression mode for local data transfer optimization
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Starting copy 2.3.0...
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Copy appname: gpcopy_202102182136_xdUY6jZpxq2uyZCG5ytf4F
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-'./gpcopy' --dest-host 'mydb-m' --dest-port '3002' --include-table 'gpadmin.public.test' --skip-existing --source-host 'mydb-m' --source-port '3000'
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Initializing gpcopy
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-pg_dump (PostgreSQL) 9.4.24
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-pg_dumpall (PostgreSQL) 9.4.24
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Source Cluster PostgreSQL GetVersion is: 9.4.24 
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Start copying database "gpadmin"
20210218:21:36:23 gpcopy:gpadmin:mydb-m:008929-[INFO]:-[Worker 3] Start copying table "gpadmin"."public"."test" => "gpadmin"."public"."test"
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[ERROR]:-[Worker 3] Finished task 29278_DL_P_DA_V_ with error:
 pq: unrecognized configuration parameter "lock_timeout"
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[ERROR]:-[Worker 3] [Progress: (0/1) DBs, (1/1) tables done] Failed to copy table "gpadmin"."public"."test" => "gpadmin"."public"."test"
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-[gpadmin] Finished copying database "Progress: (1/1) DBs, (1/1) tables done"
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-------------------------------------------------
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Total elapsed time: 1.197322329s
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Total transferred data 0B, transfer rate 0B/h
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Copied 1 databases
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-    Database gpadmin: successfully copied 0 tables, skipped 0 tables, failed 1 tables
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-      Failed tables list:
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-        "gpadmin"."public"."test"
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Successful table list will be saved into 'gpcopy_202102182136_xdUY6jZpxq2uyZCG5ytf4F_success.list'.
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-Failed table list will be saved into 'gpcopy_202102182136_xdUY6jZpxq2uyZCG5ytf4F_failure.list'.
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-[Hint] You could re-run with below command excludes successfully copied tables at last time:
20210218:21:36:24 gpcopy:gpadmin:mydb-m:008929-[INFO]:-    './gpcopy' --dest-host 'mydb-m' --dest-port '3002' --include-table 'gpadmin.public.test' --skip-existing --source-host 'mydb-m' --source-port '3000' --exclude-table-file 'gpcopy_202102182136_xdUY6jZpxq2uyZCG5ytf4F_success.list'

 

Cause

 

Resolution

Create an empty table with the same DDL as the source table in the target database and run the gpcopy with "--append" or "--truncate" option.