DSXchange

We've found a problem when we tried to upload to Netezza the data that we got from Sybase, this issue arose specifically with the floating points data types. Then, we found out that the issue is not from any of the databases, but from datastage itself.

The test that proves it is the Row Generator when we try to write into a Sequential File.

The issue is that we need a period as a decimal mark, in all the numeric data type (double, float real, decimal, numeric). But the floating point data types (Double, Float, Real), which are written in Scientific Notation, have a comma instead. The fixed point data types(Decimal, Numeric) doesn't have any problem because when we change the decimal delimiter, it changes correctly.




We've tried changing the Default Decimal Delimiter, the NLS, and some other Locales in datastage and regional settings in windows server, but the problem persists.

We want to keep the Sybase datatype to the destination database.

We truly appreciate any help!
Regards

You might also want to test Row Generator stage to Peek stage, to remove the database stages and the Sequential File stage as variables.

The "decimal separator" as it is called in the Sequential File stage properties can be set or overridden there.

It can also be set or overridden in the job level in the job properties on the Defaults tab.

It is also set at the project level per project in Administrator on the Parallel tab.

The locales documentation also calls it the "radix character."

Thank you for your answer! Unfortunately, those are all set to period, and it still doesnt change..

qt_ky wrote:You might also want to test Row Generator stage to Peek stage, to remove the database stages and the Sequential File stage as variables.

Yeah,but for some reason the Row Gen doesn't generate decimals numbers, so the peek doesnt show the comma. Anyway, we need to pass the info through a Sequential file or Dataset stage at some point, so, even if that fix it, the problem is still there.

qt_ky wrote:The "decimal separator" as it is called in the Sequential File stage properties can be set or overridden there.

It can also be set or overridden in the job level in the job properties on the Defaults tab.

It is also set at the project level per project in Administrator on the Parallel tab.

Yeah, we set it all to period, even the locale, that should make a difference, is set to 'en_US', so it should use period..
Also, the Windows is in spanish, but we tried changing it in a virtual machine, and it didn't work.

Sequential File properties:

Job NLS and Locales:

Job Defaults

This issue is solved with the patch APAR JR58661.
Regards.

Thanks for coming back and posting your resolution!