Codepageconversion for BINARY fields in DB2 stage - why?
Posted: Thu Jan 31, 2008 2:37 am
Hi,
I can not understand the DataStage logic in DB2 stage when working with BINARY data, maybe one can help me or maybe it is a bug?
When I select binary data (DB2 datatype: CHAR FOR BIT DATA) in my DB2 stage - having NLS UTF8 - it will result in a NLS Mapping error in the log.
This means that DataStage will do a codepage conversion for BINARY data! It do not think that this is correct.
To double check I tried the same with the DB2 stage set to NLS NONE and it work fine with the expected result for the binary column. But now I do not know if the other input columns are processed as expected...
I my understanding a binary data type should never be converted or influenced by the codepage.
So I would expect that the DB2 stage (set to NLS UTF8) should convert every column but never BINARY fields. - Correct?
Thanks in advance
Michael
I can not understand the DataStage logic in DB2 stage when working with BINARY data, maybe one can help me or maybe it is a bug?
When I select binary data (DB2 datatype: CHAR FOR BIT DATA) in my DB2 stage - having NLS UTF8 - it will result in a NLS Mapping error in the log.
This means that DataStage will do a codepage conversion for BINARY data! It do not think that this is correct.
To double check I tried the same with the DB2 stage set to NLS NONE and it work fine with the expected result for the binary column. But now I do not know if the other input columns are processed as expected...
I my understanding a binary data type should never be converted or influenced by the codepage.
So I would expect that the DB2 stage (set to NLS UTF8) should convert every column but never BINARY fields. - Correct?
Thanks in advance
Michael