loading float value
Moderators: chulett, rschirm, roy
loading float value
I am extracting data from sequential file and load into Teradata table, In table one column datatype is 'float'. Here I am getting the following error.
Error when checking operator: Type mismatch for field 'RSK_NO'. Fatal error.
Teradata_Enterprise_241: Error when checking operator: Input record and output table schemas are not compatible.
Error when checking operator: Cannot prepare target table.
Please suggest me, how to load float values in teradata
Thanks
IBMDS
Error when checking operator: Type mismatch for field 'RSK_NO'. Fatal error.
Teradata_Enterprise_241: Error when checking operator: Input record and output table schemas are not compatible.
Error when checking operator: Cannot prepare target table.
Please suggest me, how to load float values in teradata
Thanks
IBMDS
IBMDS
What (exactly) have you declared the column's data type to be in Teradata? And what data type in DataStage?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
IBMDS - how many digits of precision? The message,
is pretty clear that somewhere there is a discrepancy. How did you determine the Teradata DDL?Type mismatch for field 'RSK_NO'. Fatal error
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
In the Float metadata have you enable "allow all zeroes"?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Try importing the table definition using Orchestrate orchdbutil facility. Compare the two table definitions to see whether there are any differences. Even if you can't see any, replace the table definition in the job with the one imported using orchdbutil, and see whether that solves the problem. The orchdbutil facility is known to handle metadata more accurately than other importers.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Did you fix this error? We had the same problem using decimals, as our TD supports a maximum of decimal(18) so when we had to populate a 38,2 we simply defined it as an 18,2 in DS.
3NF: Every non-key attribute must provide a fact about the key, the whole key, and nothing but the key. So help me Codd.