ORACLE Data conversion warning

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
UPS
Premium Member
Premium Member
Posts: 56
Joined: Tue Oct 10, 2006 12:18 pm
Location: New Jersey

ORACLE Data conversion warning

Post by UPS »

We are getting the following warning message during our load:

"Implicit conversion from source type "dfloat" to result type "decimal[18,2]": Possible range/precision limitation."

The source definition is a 'double' and the target is NUMBER(18,2).

Any suggestions?
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

What is the length and scale of the double field? It might be more than the target and hence the warning.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

This is a warning in the sense of an alert, rather than anything necessarily being wrong. Both "double" (SQL terminology) and "dfloat" (Orchestrate terminology) mean "double precision floating point number". These are huge beasts, and can certainly contain more than 18 significant digits.

You can demote the warning to informational with a local message handler, or you can add a data type conversion (Modify or Transformer stage) in your job. The Modify stage can have an additional Specification property containing the single token NOWARN to suppress generation of this kind of warning.
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