One possible workaround (ugly but should work) is to change the data type in the Source Definition to a VARCHAR (no joke!) of sufficient length. This should ensure that the records are "translated" by the Teradata driver from a DATETIME WITH TIMEZONE to a string value (of course in the "native" Teradata format).
Unfortunately I have no idea whether Teradata PT can perform this kind of conversion. You will have to try. If that doesn't work, could you please try the "normal" Teradata driver (ODBC, if memory serves me right)? I know, you're concerned about performance, but I don't know Teradata good enough to make any other useful suggestion.
Correct, PowerCenter does not support Timestamp with Timezone datatype in Teradata. As for some workaround, you could:
1) Truncate the timestamp 32 and make it a supported size during import.
2) Import it as String
3) Use Java Transformation and use -Duser.timezone is passed to the JVM as KB: Support
Thank you so much Nico....
As suggested, I have updated the such fields in source definition in Informatica with datatype as String instead of TimeStamp with Timezone. This worked perfectly fine with Teradata PT Connection.
Point#2 worked for me.
Thank You so much.