loading float value

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
IBMDS
Participant
Posts: 20
Joined: Thu Nov 09, 2006 1:58 pm

loading float value

Post by IBMDS »

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
IBMDS
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

What (exactly) have you declared the column's data type to be in Teradata? And what data type in DataStage?
IBMDS
Participant
Posts: 20
Joined: Thu Nov 09, 2006 1:58 pm

Post by IBMDS »

In teradata table, its float and in DataStage also defined as float
IBMDS
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

IBMDS - how many digits of precision? The message,
Type mismatch for field 'RSK_NO'. Fatal error
is pretty clear that somewhere there is a discrepancy. How did you determine the Teradata DDL?
IBMDS
Participant
Posts: 20
Joined: Thu Nov 09, 2006 1:58 pm

Post by IBMDS »

The source data looks like this

0.0302841
0.143932
0.044229
0.0474514
0
0.099517
0.00209654


Thanks
IBMDS
IBMDS
IBMDS
Participant
Posts: 20
Joined: Thu Nov 09, 2006 1:58 pm

Post by IBMDS »

I imported table using plug-in metadata definition. its float and i verified the table(show table in teradata). its defined as float.

Thanks
IBMDS
IBMDS
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

In the Float metadata have you enable "allow all zeroes"?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

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.
battaliou
Participant
Posts: 155
Joined: Mon Feb 24, 2003 7:28 am
Location: London
Contact:

Post by battaliou »

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.
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

You just replied to a 4-year old message.
Choose a job you love, and you will never have to work a day in your life. - Confucius
Post Reply