I will have this looked into. A few notes:
1. please provide the version of TPT you are using.
2. Although not harmful, you are putting in attributes and values that do not pertain to the operator definition. They will be ignored, and thus I am not sure if it will impact results you are expecting. For example: DropMacro and MaxDecimalDigits are not valid for the LOAD operator.
Why are you specifying the delimiter as a hex value.
Please just use the Delimiter attribute and set it to '|'.
We have data sets containing pipe as valid data and hence going with hex-10. I will try loading them without MaxDecimalDigits.
TPT Version: Teradata Parallel Transporter Version 14.10.00.05
Ok, this is inconsistent with the presented problem.
You stated, "Data is pipe delimited".
If the data is pipe delimited, then you do not need to provide a delimiter character, as that is the default. If you want to specify it anyway, you need to use the Delimiter attribute and set it to '|'.
If your data contains the pipe character, then you MUST enclose the field in quotes. And then you will need to use the QuotedData attribute.
To illustrate the problem, I have used pipe. Here is how data looks like, we are using hex-10 as delimiter and that is what we have in the input file for TPT load.
12345^P1234567^P"abcdef" Lane^P1234^Pxnybkhhh^P2015-04-25 10:00:00
Please send me the .out log file to my email:
I am using tdload from ttu14.10 and received the below error:
Can this be handled using tdload. We are not using TPT script.
The error message indicated column 6.
Was the data you provided the actual entire record?
Or did you remove some of the data (with or without quotes, I do not see at least 6 columns).
I am asking to figure out if there is more than one problem going on.
But to answer your question, not every feature of TPT is available in Easy Loader (tdload).
And "quoted delimited data" is one of them, and we are working on enhancing that feature and backporting to prior releases.
Thus, there will be an upcoming efix (patch) for TPT 14.10 that will allow the user to have access to all TPT features (usually enabled through operator attributes) through the use of job variables.
Thank you Steve. Sorry, I had to remove some portion of the record before posting in the forum.
I did couple of tests using ttu 13.10 and ttu 14.10
With the record as is: |"lot"most^who=mother|concern
tdload was successful for 13.10 and failed for 14.10
After I corrected the record
I could successfully load the file using ttu 14.10
Ok, so this is a regression.
If you do not mind, please send me the tdload command, the DDL of the target table and an entire row of data (a row that fails) so that I can work on this inhouse.
What specific version of TPT 14.10 are you using?
(Need to check in case we fixed this in a patch.)