Exact version is 14.10.00.05.
Table DDL and record that failed are as below:
In the mean time, I tried creating a tpt script to load this data. I used the below attributes for the data connector.
DEFINE OPERATOR FILE_READER_OPERATOR
I changed the attribute list to below, where I changed the character used for OpenQuoteMark and CloseQuoteMark from the default double quotes (") to single quote (').
Then the TPT script was successful.
In 13.10, we did not support quoted delimited data.
Thus, the field in question:
would have loaded with the quote characters included in the data.
Starting in 14.0, we added the feature and when you enable it, your data has to adhere to the parsing rules.
And the fied in question does not follow the rules and that is why the error is generated.
A direct link to the documentation and a few examples would really help here. Specifically, I was looking to how to export into a format MS Excel would understand and failed to find it here or in Google. Fortunately somebody else in my company has put the solution on our internal wiki. Not sharing myself it as unclear about copyright etc. :-(
i am using TPT 15.10 to export data directly export data to HDFS, but i am having issue with EscapeQuoteDelimiter and EscapeTextDelimiter both are ' \ ' this is giveng me problem when escape char itself is part of data
If Teradata value :- "abc\","sad","def"
Expected output :- "abc\","sad","def"
This is coming as expected on my dev Teradata and Dev cluster, but on my production Teradata and production cluster same script giving me the output as
this is giving me problem while parsing the data, is this something related to database settings
TPT Version on my Dev
Only big diffrence is between version PMHEXDMP, what is it is that the root cause for the problem i am facing