Archives of the TeradataForum
Message Posted: Fri, 11 Aug 2006 @ 20:33:27 GMT
<-- Anonymously Posted: Friday, August 11, 2006 16:19 -->
The error message is from Informatica, not from Teradata. I normally get this error, when my Teradata login is wrong or my log table database is full. Also there will not be an mload log file if this happens as there needs to be a successful logon for mload to execute the command ".ROUTE MESSAGES WITH ECHO TO FILE ':CF.LogFileName' ;".
To verify this, in the mload connection string, check "IS STAGED" flag. This will write the file first instead of a pipe. Ignore informatica given mload error, if it gives the same error again. Then run the mload manually using the Informatica generated mload script and see what error you are getting.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 15 Jun 2023|