Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Error Insert To Table Postgree from Oracle table

Dear All,

 

please help, i try create talend job, to insert data from Oracle into Postgree Table, but have error

this the job that i created

Starting job SelectInsert at 14:12 07/09/2018.

[statistics] connecting to socket on port 4048
[statistics] connected
Batch entry 0 INSERT INTO "migration_corp" ("ID","CD","NM") VALUES (53E47738266B401AA9FE263CC502EC45,PCM0000011,YENNY NOVITA) was aborted.  Call getNextException to see the cause.
caused by: ERROR: column "ID" of relation "migration_corp" does not exist
[statistics] disconnected
Job SelectInsert ended at 14:13 07/09/2018. [exit code=0]

0683p000009LzOL.png0683p000009LzSW.png0683p000009LxX1.png

Labels (2)
2 Replies
manodwhb
Champion II
Champion II

@Chaerul8s,in PostgreSQL , i believe already Id column will be by default winch will auto generates, you need to change to different field instead.

ankit7359
Creator II
Creator II

Hi @Chaerul8s

Good to see that u want to insert data from one DB to another(Oracle to Postgres in your case).

First thing what i would like to suggest is.... it is better if u use metadata/repository connection rather than using connection components.

Second is that, pls check the table onto postgres...so my question is have u created the table onto postgres manually or do u want create the table using talend ???

From what i see.. u might have created the manually.... so in the action on table pls give drop table if exists and create and action on data is insert by default...

Also i have noticed that the datatype for ID is string(No issues),but in the source side there is no length defined while at the target u have given some length.

Normally u r scenario will work 100%...

pls check for few basic things....u will be good to go 

also the id column is not default in postgres - that would happen only if there is a sequence