Arabic Character issues in Sequential File
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 23
- Joined: Sun Aug 01, 2004 2:33 am
- Location: Dubai
- Contact:
Arabic Character issues in Sequential File
Hi All
We have a problem in Arabic Characters while processing the data from Oracle 9i table to Sequential File, but the same Job was success full when we were processed between Oracle to Oracle tables. What will be the problem? If the NLS setting installation then please let me know where I have to look into it and how to trouble shoot this issue.
The NLS setting we are using ISO8859-6, MS1256.
We have a serious issue on this any one help it will be great.
Thanks and Regards
Regi Paulson
We have a problem in Arabic Characters while processing the data from Oracle 9i table to Sequential File, but the same Job was success full when we were processed between Oracle to Oracle tables. What will be the problem? If the NLS setting installation then please let me know where I have to look into it and how to trouble shoot this issue.
The NLS setting we are using ISO8859-6, MS1256.
We have a serious issue on this any one help it will be great.
Thanks and Regards
Regi Paulson
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Can you be a little more specific about the nature of the problem? Can you also advise the NLS parameter values from uvconfig, from the project (as set in Administrator) and from the job itself, in particular in the Sequential File stage?
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:
The "blah-CS" maps are for client/server communication. Can you try setting the map in the Sequential File stage to an appropriate UNIX map for Arabic? (If your server were a Windows server, the appropriate map would be MS1256-WIN2K; however, the Microsoft code pages are not appropriate for UNIX servers. Research the appropriate map name to use in the NLS Guide. You may need to build/load this map using the Administrator client.)
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: 23
- Joined: Sun Aug 01, 2004 2:33 am
- Location: Dubai
- Contact:
-
- Participant
- Posts: 23
- Joined: Sun Aug 01, 2004 2:33 am
- Location: Dubai
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The point I was trying to make is that MS1256-WIN2K-CS is (clearly) a map intended to be used on a Windows machine. You need to find out what the appropriate map name to use on a UNIX machine is.
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.
-
- Premium Member
- Posts: 385
- Joined: Tue Oct 07, 2003 4:55 am
Hi,
If you work on unix, use ISO8859-6 as your default map.
I assume your client machine supports Arabic.
It suspect the DS job is ok but the view-data is corrupted. I suggest you create a demo job that wrties all the letters into a sequencial file and then look at it using the command . this will show you the hex value and you can see what you realy have in the file.
I often have the same problem with Hebrew (1255)
Good luck
Amos
If you work on unix, use ISO8859-6 as your default map.
I assume your client machine supports Arabic.
It suspect the DS job is ok but the view-data is corrupted. I suggest you create a demo job that wrties all the letters into a sequencial file and then look at it using the
Code: Select all
od -cx file_name
I often have the same problem with Hebrew (1255)
Good luck
Amos
-
- Participant
- Posts: 23
- Joined: Sun Aug 01, 2004 2:33 am
- Location: Dubai
- Contact:
Arabic Character issues - Resloved
Hi All,
Thank you very much to helping me with your view and ideas, finally I had resolved the issues. I had resolved this issue with enabling MS1256-WIN2K NSL setting in DS which is comfortable in Unix NLS settings for windows version.
Once again thank you very much for all of you.
Thanks and Regards
Regi Paulson
Thank you very much to helping me with your view and ideas, finally I had resolved the issues. I had resolved this issue with enabling MS1256-WIN2K NSL setting in DS which is comfortable in Unix NLS settings for windows version.
Once again thank you very much for all of you.
Thanks and Regards
Regi Paulson