Qlik Replicate Full Load Fails with "extra data after last expected column" Due to Computed Column in PostgreSQL Target

[JoshAtBeijer]

I'm experiencing an issue during full load in Qlik Replicate, replicating from IBM DB2 iSeries (source) to PostgreSQL (target).

The replication task fails with the following error:

ERROR: extra data after last expected column
CONTEXT: COPY ABC00, line 1: "0,"TEST TEST",0,"AERFAST AAAA/BBBB","",28,28300,"","D","",0,0,"","","","","","",""...

After investigating, I found that the issue is caused by a computed stored column that I manually added in the PostgreSQL target table. This column does not exist in the source table.

When I remove the computed column from the target, the full load completes successfully.

1. Is there a way to configure Qlik Replicate to ignore computed/generated columns in the target during full load?
2. Can Qlik Replicate be instructed to match only source columns when generating the COPY command?
3. What’s the best practice for using computed columns in PostgreSQL when working with Qlik Replicate?

Any guidance or shared experience would be greatly appreciated!

Thanks,
Josh

[Dana_Baldwin]

If you haven't tried already, please put the computed column at the end/far right of the target table.

Thanks,

Dana

[JoshAtBeijer]

It is already at the end of the table.

[DesmondWOO · Accepted solution]

Hi @JoshAtBeijer ,

In the PostgreSQL endpoint, please add the internal parameter loadUsingCSV (case sensitive) and uncheck the box.

Regards,
Desmond

[JoshAtBeijer]

Thanks it is working, but it much slower than before. Does it affect CDC as well? Is there something Qlik can look to improve in future versions?