Archives of the TeradataForum
Message Posted: Thu, 22 Dec 2005 @ 11:28:32 GMT
We are having a problem with HEX '00' in data we are trying to load with
PC FastLoad, PC TPump & PC Multiload.
We are using Windows versions of the TD utilities with a pipe delimited file. Sporadic records in the input file contains a hex '00' in a Varchar(2000) field.
It appears the input process mistakenly recognizes this as the end of record which causes loss of all data in the row from the '00' to the end of the record. This results in all three load utilities to see a short record, and fail with a 'Not enough data in vartext record' error.
Since the load utility never recognizes the hex '00' in the record we have no way inside the utility to deal with the problem. i.e. nullif, case statements, etc.
The utilities also do not appear to put the record into an error table so we have no way of examining the record and inserting it later.
We are using NOSTOP to load all other records.
Is there some way to configure the input so it will accept the '00'? Or any other solution that will allow us to ignore or avoid the '00'?
Using specialized tools we can manually go into the file and do a 'replace' to replace the HEX'00' with a HEX'20', the file then loads fine, but this is not a feasable long term solution.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|