Page 2 of 2
Posted: Thu Aug 13, 2009 6:40 am
by ArndW
I don't know what to add. With an Oracle insert and a array size of 1 I don't see how a row could fail to go down the reject link.
Posted: Thu Aug 13, 2009 7:59 am
by algfr
ArndW wrote:I don't know what to add. With an Oracle insert and a array size of 1 I don't see how a row could fail to go down the reject link. ...
Thanks though.
I've just made significant progress on this...
in fact the "weird" characters and the oracle insert error are not linked...
I've just seen that setting the target oracle stage to "Sequential" mode makes it work.
Does this remind you something ?
Posted: Fri Sep 18, 2009 6:10 am
by algfr
ArndW wrote:That would not be a hex or binary viewer. The goal is to get the numeric representation of what is in that character. ...
IBM's answer :
CCSID 500 is a EBCDIC charset. Our application will not be able to work with this. You have to convert to a equivalent ASCII charset using the DD driver. Since CCSID 500 is a latin-1 charset I would think that IANAAppCodePage=4 should get the data correctly.
Regarding DataStage NLS, I think ISO-8859-1 should be fine for CCSID 500 data.
Please refer to
http://www.datadirect.com/support/troub ... /index.ssp for more information.
So I have to convert using this "DD". has anyone had the same issue ?