Archives of the TeradataForum

Message Posted: Thu, 11 Dec 2008 @ 12:38:24 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Vinay,

If your problem still not solved, Can you check the source and target table definition?

For example: in source side columns (PI/PK) are CASESPECIFIC and target (Teradata) side it is NOT CASESPECIFIC in this case it will take v089m and V089M same and give you duplicate unique prime key error.

Polesh

	<Prev	Next>		<<First	<Prev	Next>	Last>>