Special character showing as question marks in table

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
midmaxds
Premium Member
Premium Member
Posts: 71
Joined: Mon Oct 26, 2015 11:44 am

Special character showing as question marks in table

Post by midmaxds »

Hi,
We have a job which extracts records from Oracle table and loads to a DB2 table. No transformations.
The issue is with a NAME field where in Oracle and DB2 it is varchar (80).

one of the names has a non English character such a cross sign, a star etc (My keyboard does not have them, sorry)

So when the name comes to DB2 table these characters are just question marks (??).
After googling a bit we tried giving the unicode option in oracle stage. Now the data is coming as expected, but director has logs saying this could cause lose of data. Please advise on how we can get through this. Thank you.
Midhun
midmaxds
Premium Member
Premium Member
Posts: 71
Joined: Mon Oct 26, 2015 11:44 am

Post by midmaxds »

Hi,
Any thoughts, please...
Midhun
UCDI
Premium Member
Premium Member
Posts: 383
Joined: Mon Mar 21, 2016 2:00 pm

Post by UCDI »

I think the symbol you see with a ? inside it is the symbol that datastage uses to tell you that there is something there which it does not know how to display.

The loss of data warning tells me that you very likely have a metadata mismatch somewhere that is feeding a unicode enabled string into a non-unicode enabled string which damages the data. Make sure all your links/metadata have unicode on them.
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Post by SURA »

Use oracle tool to export the data into a text file and apply od command.

Try to get better hold of the data and then handle it.
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Verify with both databases whether the length is specified in BYTES or in CHARACTERS. If BYTES you will likely have problems with longer strings using multi-byte characters.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
midmaxds
Premium Member
Premium Member
Posts: 71
Joined: Mon Oct 26, 2015 11:44 am

Post by midmaxds »

Thank you all.
The issue was finally fixed by increasing the number of bytes in target database and changing data type to unicode from varchar in jobs. Thanks again!
Midhun
Post Reply