Cbcopy : Indexes issue during migration

[adnanhamdussalam]

Hi,

I did a migration test from GP version 6 to CB version 2.0 using cbcopy 1.1.3

It completely missed out the non unique index creation on target CB side no error found in the log against the index creation error.

Kindly need your support on this issue

[tuhaihe]

Hi @robertmu, could you help take a look? Thanks!

[robertmu]

Hi,

I did a migration test from GP version 6 to CB version 2.0 using cbcopy 1.1.3

It completely missed out the non unique index creation on target CB side no error found in the log against the index creation error.

Kindly need your support on this issue

Could you please provide the DDL scripts for the source table and the index from your GPDB 6?

We need this information to try and reproduce the issue locally. Thanks!

[adnanhamdussalam]

Hi @robertmu,

PFB the DDL Script:

CREATE TABLE mydata.abc (
dialprefix text NOT NULL,
recordtype text NULL,
effect_date timestamp NOT NULL,
startdate timestamp NOT NULL,
enddate timestamp DEFAULT '2099-01-01 00:00:00'::timestamp without time zone NULL,
source text NULL,
companycode text NULL,
modernizedprovider text NULL,
tos text NULL,
porttimestamp timestamp NULL,
iso2 text NULL,
dcadmindiv text NULL,
dclocality text NULL,
dcadmindivlocality text NULL,
dcutc text NULL,
rcadmindiv text NULL,
rclocality text NULL,
rcadmindivlocality text NULL,
rcutc text NULL,
portcount int4 NULL,
CONSTRAINT pk PRIMARY KEY (dialprefix, effect_date)
)
DISTRIBUTED BY (dialprefix, effect_date);
CREATE INDEX dialcodeorprefix_idx ON mydata.abc USING btree (dialprefix);
CREATE INDEX abc_dialprefix_idx ON mydata.abc USING btree (dialprefix, effect_date);

[robertmu]

Hi @adnanhamdussalam,

Thanks for providing the DDL scripts.

We tried to reproduce the issue using the provided DDL statements, but the table and indexes were created successfully in our environment without any errors.

Could you please provide the full log file for the failed migration?
You can find the log file in the $USER/gpAdminLogs directory, named cbcopy_$timestamp.log.

This log should contain the detailed error messages that will help us pinpoint the issue. Thanks!

[adnanhamdussalam]

Hi @robertmu,

Let me go through again with the testing in my environment and will update you.