Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Please look as your destination with something other than View Data. Tell us what's actually loaded. The question mark is simply a mechanism for representing "unmappable character".
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
sohasaid,
You stated that the two characters listed in the subject are coming in from
Oracle in a US7ASCII table.
Those characters are not in the 7-bit US ASCII table and therefore are not displayable and changed to '?'.
You stated that the two characters listed in the subject are coming in from
Oracle in a US7ASCII table.
Those characters are not in the 7-bit US ASCII table and therefore are not displayable and changed to '?'.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
The issue is that you don't know what character set you are using in your database (the 7 bit one is patently incorrect), so you won't be able to get DataStage to read it correctly using NLS. Go into DB2 and enter 'get db cfg for {your database};'
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Ok, then your source is Oracle. The two characters you've listed cannot be stored in 7bit ASCII, internally your Oracle is using another character set. You've specified that Oracle converts from the internal character set to 7 bit ASCII and it is there that you are losing these character values. Find out, from your DBA, what character set is being used for this table and set your environment variables accordingly.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 8
- Joined: Tue Dec 16, 2008 12:11 pm
US7ASCII DB can have 8Bit data inserted into it
The Character set enabled at the entry device(Keyboard) may have latin accents enabled. The data entry person can then enter these into the GUI and the DB will compress the 8Bit data into a 7Bit field (Lossy data). This data will then appear to be wingdings, Arabic, upside down question marks etc. I have encountered this problem twice before. The SQL tool, DataStage will Select and Read the data as is (Lossy) but the target DB will reject the data with error messages like data inserted is to large for field definition. To date I have not figured out how to overcome this aside from "cleansing" the data at the source.
Both clients have refused to convert their source DBs to an 8Bit NLS.
Both clients have refused to convert their source DBs to an 8Bit NLS.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: