Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

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


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


Subj:   Re: ML Error 2801: Duplicate unique prime key
 
From:   Polesh Pardhi

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>>
 
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020