Float Datatype handling - Conversion from dfloat to sfloat

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
RudreshEswarappa
Participant
Posts: 21
Joined: Wed Aug 29, 2007 1:33 am
Location: Bangalore
Contact:

Float Datatype handling - Conversion from dfloat to sfloat

Post by RudreshEswarappa »

If there is a float field in the destination, i am getting the below error.

APT_CombinedOperatorController(1),1: Fatal Error: Accessor type "sfloat" does not match interface field type "dfloat".

If i convert it into integer, it works. But i need to convert it in to float datatype.

Can anyone help me to do this conversion??

Thanks in Adv.

Rudresh
Rudresh Eswarappa
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You don't need to do anything, provided that the number supplied as a dfloat is small enough to be represented as sfloat. (It is the possibility that it may not be that you are being alerted to.) If you are 100% certain of this, add a message handler to demote the alert to informational.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
RudreshEswarappa
Participant
Posts: 21
Joined: Wed Aug 29, 2007 1:33 am
Location: Bangalore
Contact:

Post by RudreshEswarappa »

But the job fails on execution, though both the source as well the destination are of type float.

The error message given is

APT_CombinedOperatorController,2: Fatal Error: Accessor type "sfloat" does not match interface field type "dfloat".

Everything is fine in the job, Can anything be done about it".



Regards

Rudresh
Rudresh Eswarappa
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Disable operator combination and find out where the error is occurring. That may yield some ideas.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
RudreshEswarappa
Participant
Posts: 21
Joined: Wed Aug 29, 2007 1:33 am
Location: Bangalore
Contact:

Post by RudreshEswarappa »

Sorry again.

"I am using ODBC enterprise as my source, and here i do not have any options for Disable operator combination.

I have already disabed the schema reconciliation by setting to 'NO' both 'fail on type mismatch' and ' fail on size mismatch'. "

Its the same result. I have got it to work now by converting the datatype at the destination table to Int.

Regards
Rudresh
Rudresh Eswarappa
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You have APT_DISABLE_COMBINATION available.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply