DB Number Columns (no scale/precision) give warnings

[roy]

Hi All,

I have a situation where DB tables have some numeric columns defined as number , with no sacle/precision defined.
DS imports their definition as decimal(38,10) due to lack of info, which causes some problems like:
writing an 7 digit number to a data set gives a decimal(38,10) number with leading and trailing zeros to the full 38 and 10 scale/percision mentioned (...000000012345678.00000...).
warnings for conversions and disk space and more.

I'm interested in work arounds for cases I can't redefine the columns with proper scale,precision and still get a proper number x digit integer number.

I'm gathering ideas and was wondering of what you might use or can think of for this case.

Thanks in advance,

[richdhan]

Hi Roy,

Are you using Oracle as DB? With oracle the columns that are defined as Number are by default getting imported as Decimal(38,10). We use the DecimalToDecimal function avialable in Transformer to reduce the size as well as the precision.

HTH
Rich

[ray.wurlod]

From memory, you can also adjust precision and scale with a Modify stage. Just specify the correct values on input and output links, and supply the appropriate function if automatic casting is not possible (which you can determine from the manual).