Archives of the TeradataForum
Message Posted: Fri, 08 Dec 2000 @ 22:27:14 GMT
Michael Larkins wrote:
Your note piqued my interest. I assumed that the 2679 error was one of the RDBMS messages, not an MLoad-specific error. Looking it up, I found that older documentation (B035-1011-108A, for version 3.0.0) contained the following description:
2679 The format or data contains a bad character
Explanation: This error occurs when the user submits a numeric-to-character conversion with an illegal format, or when, in converting characters to numeric, either the data or the format contains a bad character.
Remedy: Validate the format used. If it is legal, then an illegal character is present in the data being converted from character to numeric.
However, when I looked in more recent documentation (B035-1096-060A, for version 4.0.1), I found a different write-up:
2679 Specified %VSTR does not exist in %DBID
Explanation: A table was dropped before a statement that references the table was processed.
Remedy: The table that is referenced no longer exists. If it is needed, it must be re-created.
Obviously that isn't going to be of any help (although the first error message seems to match your situation). Looking in the current MLoad manual (B035-2409-090A, for version 4.0.1), there is an example of analyzing an error and wouldn't you know it, the manual uses a 2679 for their example. I found the example on Page 2-72. There's really not a lot there, but you might take a look.
Other than my 2 cents, Mike Larkin has made some pretty solid suggestions.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|