Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 05 Jun 2014 @ 10:16:29 GMT


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


Subj:   Duplicate unique prime key error encountered for ODBC Teradata Session Mode
 
From:   Nachor, Sherwin

Hi All,

I need some help. We are encountering this error when the ODBC connection was configured to use Teradata Session Mode? The records are successfully being inserted when using ANSI Session Mode. Please see below the sample target table definition. Any help will be greatly appreciated. Thank you.

     CREATE SET TABLE SampleTable ,NO FALLBACK ,
          NO BEFORE JOURNAL,
          NO AFTER JOURNAL,
          CHECKSUM = DEFAULT
          (
           Col1 VARCHAR(8) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
           Col2 SMALLINT NOT NULL,
           Col3 TIMESTAMP(6) NOT NULL,
           Col4 CHAR(5) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
           Col5 DECIMAL(18,0) NOT NULL,
           Col6 DATE FORMAT 'yyyy-mm-dd',
           Col7 BYTEINT,
           Col8 VARCHAR(255) CHARACTER SET UNICODE NOT CASESPECIFIC,
           Workflow_Run_Id INTEGER NOT NULL)
     UNIQUE PRIMARY INDEX (Col1, Col2, Col3, Col4, Col5);

Please note that the values in all the columns included in the UPI are unique in all records.


Best regards,

Win



     
  <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