We have a table which we are exporting from Teradata using TPT.The script is failing when we include a column in the extraction query.The column has type decimal(38,18).
In the schema we have defined the column as col1 DECIMAL(38,18).
When we use the column in the extraction query the script fails with a "Schema Mistmatch" error.The same thing works with decimal columns with less precisions DECIMAL(8,2) for instance.Is there some kind of limitation.Teradata version is 13.00
Have you tried setting the MaxDecimalDigits attribute? I think you'll find that on a network attached client it defaults to 18 digits.
I have set the MaxDecimalDigits attribute to 38.Now the script is running successfully but the data we are getting wrong data in the exported file.
We have data like 334.454566776776000000 in the table but we are getting 0 in the output file.
Have you checked that the SELECT statement is returning valid values (i.e. is it the SELECT or is it TPT)?
- run it using SQLA or Studio etc.and check the output.
- if the normal output has too many rows to do this then add to the WHERE clause to only select those row(s) that are showing this symptom.
What client system are you running on?
What format is the data being written out in (binary, text etc.)?
The SQLA is returning proper values.The problem is arising only in the TPT script output.
We are using Teradata database 13.00 and Teradata SQL assistant 15.0.TPTversion is also 15.00
Can you share your TPT script?
Are you using the latest maintenance level of TPT 15.0?
Note that TTU 15.0 is now over 3 years old, and regular maintenance has been discontinued.
There were also a number of changes and improvements related to "large decimal" in TPT 15.10.01 and later.
How to check if we are using the latest maintainance level?The TPT version shows 15.00.Is there any way to verify?
From the command line on your client system (where you run TPT from) just run the tbuild command (no parameters).