Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

Message Posted: Thu, 08 Mar 2007 @ 22:26:18 GMT


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


Subj:   Re: Exiting on BTEQ errors
 
From:   McCall, Glenn David

  Hmmm, what more can I say? Perhaps you need to post an example!  


Of course I could say if the example I used was better, I would see the problem.

Interestingly if I put an error in my SP e.g. insert into Non_existant_table values (...);

Then I get an error, but the SP is also replaced with the error in it. If I call the SP, I get an error 3807: "Non_existant_table" does not exist.

So I'm sorry, but I don't know how to check for this other than scraping the bteq output with Perl or similar.

For what it is worth, even the error code isn't being set. So commands like:

     .compile file=t.spl
     .if errorcode > 0 then .quit 1

Doesn't cause the bteq script to abort.

It isn't even worth dropping and creating the procedure and doing a select on the procedure name from dbc.tables (and checking activity count of 0) as the erroneous procedure seems to be created.


Glenn Mc



     
  <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