Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 25 May 2004 @ 15:41:17 GMT


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


Subj:   Re: Identifying row which caused 2802 Error (Duplicate Row)
 
From:   Michael Larkins

Hi Phillips:

Without knowing a single thing about your table, I am guessing that you are doing a join within the UPDATE statement to identify which row to UPDATE or to obtain the data for the change.

Either case, from the error you are receiving, it sounds like maybe you are doing a product join. By looking at the EXPLAIN output, you can verify this. If not a product join, it sounds like you have not specified enough columns in your WHERE it make the join unique. I have seen this error under these circumstances because what it attempts to do in INSERT a copy of each row with the new value. Hence, the duplicate row error. In the old days, it would have inserted new rows into your table - these the are same ones we called the "good old days"...lol

My recommendation is that you go back to your logical model and verify that you are using enough columns to make each row unique.


Hope this helps,

Michael Larkins
Certified Teradata Master



     
  <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: 27 Dec 2016