Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 03 Feb 2004 @ 21:29:09 GMT


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


Subj:   Is there an SQL error table?
 
From:   Richard Gomez

We are in the midst of an upgrade from V2R3 to V2R5, and are trying to test our legacy processes on the new system and have hit a few snags. One of the problems we are encountering is capturing errors in some of our queries. There is some logic built into the legacy code that, will return and record SQL errors, however some of the errors are not captured. I know DBC.AccessLog (DBC.AccLogTbl) can record the full SQL statement (which is what we want), but the column "result" is always "G" (I would assume that this means "good"). Is there a table or setting that will record bad SQL with error codes? We would like to be able to check for possible errors in our SQL that may have occurred during our processes (the ones that may have slipped through our error checks/recording). Does anyone know if anything like this exists in Teradata, or do we have to make our process "smarter" to capture/record the errors


Thanks in advance.

Rich Gomez



     
  <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