ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIB Encoding Issue on ODBC Oracle with NLS_LANG AR8ISO8859p

Post new topic  Reply to topic
 IIB Encoding Issue on ODBC Oracle with NLS_LANG AR8ISO8859p « View previous topic :: View next topic » 
Author Message
eammnsh
PostPosted: Sat Oct 08, 2016 12:22 am    Post subject: IIB Encoding Issue on ODBC Oracle with NLS_LANG AR8ISO8859p Reply with quote

Apprentice

Joined: 22 Aug 2016
Posts: 29

Hi All,
My Environment is as follow:
-IIB 10.0.0.4 and MQ 8.0.0.4 on Linux Redhat
-Oracle 10 g with NLS_LANG =AMERICAN_AMERICA.AR8ISO8859p6

I am already connected to the Oracle through an ODBC Data Source, configured in the odbc.ini file on the server, and the connection is working fine, as I can insert,update, and retrieve data.

But the issue is that the Database contains Arabic data, which appears to be corrupted when it reaches the IIB. I tried using CCSID 1208,1200,1089,1252, etc.. either or both by casting the fields and by setting it in the MQMD header, but still the characters are corrupted.

After some investigation I reached to two points: Either

1- I have to change the NLS_LANG to the same used by the Oracle engine on my oracle client side, but where can I reflect this change? I checked the ODBC configuration and I cant find any attribute related to encoding.

2-I have to go through all the stored procedure which my IIB call and use the convert from AR8ISO8859p to WE8MSWIN1252 on the db level, but it doesn't make sense to go through them all and convert all the retrieved fields, right?

Thanks in Advance
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Oct 08, 2016 5:33 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

So what is the language set to on your broker box. Does it support what you want?
Once you retrieve the data you may need to convert from the native code page to UTF-8 or CCSID 1200...

Also please define appears to be corrupted. If the right byte sequence is there there is nothing corrupted. You may just have an inability of the os to display the said codepage...


_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
eammnsh
PostPosted: Sun Oct 09, 2016 11:20 am    Post subject: Reply with quote

Apprentice

Joined: 22 Aug 2016
Posts: 29

This what I have tried, I tried converting to many ccsids but the data still corrupted, and by corrupted I mean some words' characters dont appear correctly.

Anyway, for now I had to create views on the db and use the db convert function.

I will post more details about the issue, if you are intrested.
Back to top
View user's profile Send private message
adubya
PostPosted: Sun Oct 09, 2016 11:58 am    Post subject: Reply with quote

Partisan

Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK

How are you verifying that the data retrieved is corrupted ? What steps do you go through to check/verify the data ?
_________________
Independent Middleware Consultant
andy@knownentity.com
Back to top
View user's profile Send private message Send e-mail
rekarm01
PostPosted: Mon Oct 10, 2016 4:30 pm    Post subject: Re: IIB Encoding Issue on ODBC Oracle with NLS_LANG AR8ISO88 Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415

eammnsh wrote:
I am already connected to the Oracle through an ODBC Data Source, configured in the odbc.ini file on the server

Using which driver? Which NLS_CHARACTERSET was used to create the database? What are the Oracle datatypes for the columns that contain Arabic data?

eammnsh wrote:
But the issue is that the Database contains Arabic data, which appears to be corrupted ... by corrupted I mean some words' characters dont appear correctly.

For example ... which words? Which characters? What should they look like? What do they look like? Can you convert the character data to hex bytes, and post a sample of that?

eammnsh wrote:
1- I have to change the NLS_LANG to the same used by the Oracle engine on my oracle client side, but where can I reflect this change?

At the very least, it needs to be a compatible character set. NLS_LANG is an environment variable; the broker .profile is a common place to set that.

eammnsh wrote:
2-I have to go through all the stored procedure which my IIB call and use the convert from AR8ISO8859p to WE8MSWIN1252

If it's necessary, then it might make more sense to convert to windows-1256, rather than windows-1252.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIB Encoding Issue on ODBC Oracle with NLS_LANG AR8ISO8859p
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.