Exporting NaN Values from Aster Decimal/Numeric Data Types When High Precision Mode of Informatica is Enabled - Aster Client

Teradata Aster® Client Guide

Product
Aster Client
Release Number
7.00
Published
May 2017
Language
English (United States)
Last Update
2018-04-13
dita:mapPath
hki1475000360386.ditamap
dita:ditavalPath
Generic_no_ie_no_tempfilter.ditaval
dita:id
B700-2005
lifecycle
previous
Product Category
Software
The Informatica connector uses a double to store Aster decimal values without high precision mode and a decimal (treated as BigDecimal in Java API) in high precision mode. Only double allows NaN values while INFA decimals (like BigDecimal in Java) do not. But Aster allows NaN values for both its double and decimal types. When high precision is disabled, NaN is exported correctly since INFA uses double to store it. But when high precision is enabled, there is no equivalent representation for NaN in Java's BigDecimal as well as INFA's decimal.

As a workaround, the Informatica connector gives a data conversion error and allows you to provide a replacement value for NaN values when Aster is a source and High Precision has to be used. You can provide "null" or any other valid number as a replacement.

The exception that is thrown when a NaN value is encountered looks similar to the following:
[ERROR] Reading data failed [Cannot convert NaN Values.] for Aster_nCluster type [NUMERIC]
  1. Go to the PowerCenter Workflow Manager and open the Task Developer.
  2. Select Edit Task.
  3. Select the Mapping tab.
  4. Under Sources, change the value of the property NaN Replacement for High Precision to null or 0.