Archives of the TeradataForum
Message Posted: Fri, 07 Jan 2005 @ 18:00:06 GMT
I have noticed in the past that if I run bteq via a unix shell script, I don't always get the error messages that are visible on the screen (if run to the screen) and they do not show up in the log. I generate the log using something like the following for cron jobs.
script.ksh > script.log 2>&1
If I am running it so I can monitor the output (and see the error messages) I do this:
script.ksh | tee script.log 2>&1
I am sometimes able to figure out I have an error because successful SQL statements will have the following below them, where unsuccessful ones (ones with error messages on the screen) will have just the elapsed time line.
*** Query completed. One row found. 2 columns returned. *** Total elapsed time was 1 second.
Is there a better way that will allow me to capture the errors? Keep in mind that 'normally' I do not run it so I can see the output, usually it is done via cron.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|