Archives of the TeradataForum
Message Posted: Mon, 30 May 2011 @ 14:16:41 GMT
| Subj: | | BODS/Teradata mload issues |
| |
| From: | | s.srilakshmi |
Hi,
We have a strange problem while executing the BODS job which loads data into teradata table using mload bulk loading option.
BODS job will generate the .ctl files during run time and the issue is the mload script i.e., the code in the .ctl file is being generated with
some incorrect commands. Can anyone with BODS/Teradata experience on loading data into teradata using mload through BODS jobs, please let me know
what could have been possible issue that the mload scripts are not being generated properly, is it something to do with the taget teradata
table?
I opened the ctl files and checked that there are some spl characters being generated in the control file because of which these error are
coming. Can anyone tell me the reason why the control files are being generated with junk characters? Any pointers on this would be really
helpful.
These are few error messages we are getting while executing jobs with teradata multiload. The same job/code without any change has been
executing succesfully sometimes and sometimes throwing below errors. Can any one please help give suggestions with respect to the issues we are
facing
-------------------------
Teradata failed with the following error: <
UTY0005 Bad data in the FIELD command at position 15, the name beginning with "VARCHA" is
not a valid data descriptor.
>. Please run with script
on the command line to debug or notify Customer Support.
-------------------------
Teradata failed with the following error: . Please run with script
on the command line to
debug or notify Customer Support.
-------------------------
Teradata failed with the following error: <
UTY2403 An invalid statement was found before the .LOGON statement.
>. Please run with script
on the command line to debug or notify Customer Support.
| 
