topic Re: ORA-00001: unique constraint (RELATE.PK1) violated in Talend Studio

ORA-00001: unique constraint (RELATE.PK1) violated

Anonymous — Mon, 27 Nov 2017 04:34:17 GMT

Hi all,

im getting this error even though i am inserting unique value in the columns mentioned,

can anyone help me

Re: ORA-00001: unique constraint (RELATE.PK1) violated

TRF — Mon, 27 Nov 2017 07:45:54 GMT

Hi,

If you are sure there is no duplicate rows in your import, is the target table empty?

Is there any trigger fired on the db which may produce duplicates for this table or an other?

Hope this helps.

Re: ORA-00001: unique constraint (RELATE.PK1) violated

Anonymous — Mon, 27 Nov 2017 09:16:35 GMT

hi sorry now im facing this issue

Message: ORA-01400: cannot insert NULL into ("RELATE"."CST_CUSTOMER"."CUST_ID")

Re: ORA-00001: unique constraint (RELATE.PK1) violated

Anonymous — Mon, 27 Nov 2017 09:20:51 GMT

even though the source column has value,

i have mappped the soapui response side CUSTOMERACCOUNTID '300000002158900' to CUSTID '1' value in database

the source side has value to be put into database,

i need help in this

Re: ORA-00001: unique constraint (RELATE.PK1) violated

TRF — Mon, 27 Nov 2017 09:25:23 GMT

Change the destination to a file or use a tLogRow or run the job in debug mode to be sure the field has a value before to enter the tOracleXxxx component.

Re: ORA-00001: unique constraint (RELATE.PK1) violated

Tool_Tip — Thu, 14 Aug 2025 04:21:05 GMT

We are facing same error in qlik compose task
"Terminated: sqlstate 23000, errorcode 1, message ORA-00001: unique constraint (DWH.abc)"

We have checked source table, CT table, TSTG table and target table none of the table has any of the duplicate records.....