Decimal value is out of range
Posted: Fri Oct 06, 2017 8:23 am
Hi,
One of my datastage jobs is failling with below error in SCD stage.
Fatal Error: APT_Decimal::asIntegerU64: the decimal value is out of range for the integer result.
Job design: Source(oracle) ->Transformer -> SCD -> Target(oracle)
The issue is with dummy record (Surrogate Key = -100) in the dimension table. There are 2 columns in source (key value pair). If the source key matches with the dummy record in target, ETL job is failing.
Dummy record (target dimension table):
SurrogateID Key Value
-100 N/A N/A
I was able to resolve the issue with either of 3 approaches, but still want to know the actual reason of failure.
a.) Filtered out 'N/A' key from source.
or
b.) Changed data type of surrogate key from Decimal(38,0) to Integer (10) and job runs fine without filtering the 'N/A' record in source.
or
c.) Using abs(surrogate key) while fetching data from target to SCD stage for comparison.
I searched forums and the suggestion given by ArndW for this issue was to contact IBM support.
viewtopic.php?t=147220
Please help on this.
One of my datastage jobs is failling with below error in SCD stage.
Fatal Error: APT_Decimal::asIntegerU64: the decimal value is out of range for the integer result.
Job design: Source(oracle) ->Transformer -> SCD -> Target(oracle)
The issue is with dummy record (Surrogate Key = -100) in the dimension table. There are 2 columns in source (key value pair). If the source key matches with the dummy record in target, ETL job is failing.
Dummy record (target dimension table):
SurrogateID Key Value
-100 N/A N/A
I was able to resolve the issue with either of 3 approaches, but still want to know the actual reason of failure.
a.) Filtered out 'N/A' key from source.
or
b.) Changed data type of surrogate key from Decimal(38,0) to Integer (10) and job runs fine without filtering the 'N/A' record in source.
or
c.) Using abs(surrogate key) while fetching data from target to SCD stage for comparison.
I searched forums and the suggestion given by ArndW for this issue was to contact IBM support.
viewtopic.php?t=147220
Please help on this.