Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Thu, 05 Sep 2013 @ 12:50:47 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: Capturing the error cd and desc
From:   Dave Wellman


I'm not sure exactly what you want.

If you want the error code and description (your words) then you've got them. " Failed [2801] Duplicate unique primary key error in T2."

If you want them inserted into a table then BTEQ won't do this directly. This is typically done using a script (shell, windows PowerShell as appropriate) which reads the BTEQ log file and then inserts the data into a table.

If you want to know which row of data causes the problem then you can:

- run the insert but use the LOGGING ERRORS option (check the SQL manual for syntax details)

- run a SELECT looking for key values that occur in multiple rows

- INSERT/SELECT into a MULTISET table with no Unique index and do the same as the previous suggestion



Ward Analytics Ltd - Information in motion (www.ward-analytics.com)

  <Prev Next>   <<First <Prev
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023