running the ds server and having an seq.inputfile
data is extracted as char(11) for a specific field
the transformer calls a routine that handles this value and the result is numeric field (all digits) I display the field before leaving the routine, and the value is correctly displayed and should be numeric as it is the output of an arithmatic operation.
Call DSLogInfo("Arg1",Ans)
BTWSIGNA..Transformer_1 (64120701341): Arg1
the target is db2 database
when defining the target column as char(11) the value is correctly loaded
when defining as bigint the value is translated to 2147483647
Any idea / help
Thanks for all info
Best Regards, Guy Przytula
character to numeric translation
Moderators: chulett, rschirm, roy
character to numeric translation
Best Regards, Guy Przytula
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It appears that DataStage is not handling BigInt, and treating the value as Integer (signed 32-bit integer).
Check whether this is the case by asking your support provider; the real question is "is BigInt" a supported data type. It wasn't in early versions of DataStage, I haven't checked for some time.
The workaround is probably user-defined SQL that is identical to the generated SQL, crazy as that sounds, but with the SQL type in the Columns grid set to CHAR(11) even though it's a BIGINT in the database.
You may get one "metadata mismatch" warning, but it will probably work.
Check whether this is the case by asking your support provider; the real question is "is BigInt" a supported data type. It wasn't in early versions of DataStage, I haven't checked for some time.
The workaround is probably user-defined SQL that is identical to the generated SQL, crazy as that sounds, but with the SQL type in the Columns grid set to CHAR(11) even though it's a BIGINT in the database.
You may get one "metadata mismatch" warning, but it will probably work.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.