| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SYBASE database with windows-1250 charset |
« View previous topic :: View next topic » |
| Author |
Message
|
| pjanura |
 Posted: Thu Jun 13, 2013 3:59 am Post subject: SYBASE database with windows-1250 charset |
 |
|
Newbie
Joined: 13 Jun 2013
Posts: 3
|
Hi all,
i have trouble with sybase database with windows-1250 encoding. I have attached odbc configuration bellow.
I have no trouble with connection. But diacritics is broken. In my flow, that use odbc, is MQInput set to convert message into CCSID 1250.
I hope, it should be correct setup.
In debug mode everything looks fine. But after validation in sybase diacritics is broken.
Do you have some experience with this state at sybase database? Can I modify odbc configuration file, in some way that will set up expected charset?
Thanks for help
Petr
[SYBASE]
Driver=/mqsi70/ODBC/V6.0/lib/UKase24.so
Description=DataDirect 6.0 Sybase Wire Protocol
Database=BACKENDWR
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
SelectMethod=0
NetworkAddress=test-.tda,5300
SelectUserName=1
ColumnSizeAsCharacter=1
EnableSPColumnTypes=2
LoginTimeout=0
TimestampTruncationBehavior=1
XAConnOptBehaviour=3 |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jun 13, 2013 4:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Don't set MQInput to convert. Broker will convert the data when it builds the logical message tree.
Don't set mq channels to convert. |
|
| Back to top |
|
|
| pjanura |
| Posted: Fri Jun 14, 2013 3:43 am Post subject: RE:SYBASE database with windows-1250 charset |
|
|
Newbie
Joined: 13 Jun 2013
Posts: 3
|
Ok, i have canceled convert mode at MQInput. I have set Charset=cp1250. But it didnt help  Do you have some tip how to solve this issue? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jun 14, 2013 3:47 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| pjanura |
| Posted: Fri Jun 14, 2013 4:11 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2013
Posts: 3
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jun 14, 2013 4:16 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
You might check with DataDirect for an updated driver. You might also like to open a PMR after you collect MustGather doc.
The DataDirect ODBC driver uses the server-platform-configured code page value as its client code page.
For Windows, the server-platform-configured code page value can be found in the Windows registry ACP value. To locate the value, use the registry editor called regedit to navigate through the registry tree to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NIs\CodePage, which represents the platform’s ODBC code page. On the right panel, scroll to the ACP value.
For Linux and UNIX, the server-platform-configured code page value can be found by using the locale command to determine the operating system, the platform, and ODBC code page value.
Upon connection to the target, the ODBC driver queries the target database for its code page and compares the value to the server-platform-configured code page:
If the values are not equal, the ODBC driver translates from the server-platform code page to the target code page.
If the values are equal, the ODBC driver does not perform any translation. As an Open Server API, the ECDA Option for ODBC relies on Open Server for datatype conversion.
It seems that this code page conversion is not working well for your application. IBM may be able to provide some assistance in configuring the ODBC driver and DataDirect may be able to update the driver to meet your application's needs.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jun 14, 2013 4:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
To be clear, the problem you are experiencing is that you are causing data conversion to happen more than once.
As lancelotlinc says, the ODBC driver will perform data conversion for you.
Stop trying to convince it that it's not supposed to, by randomly setting CCSID in various places or telling other things to perform data conversion.
Step back, let Broker convert incoming messages into the internal code page used for logical message trees. Let Broker present that data as is to the ODBC drivers, and let the ODBC driver do any needed conversion.
Once you have really honestly cleared the slate like that, and you are still having problems with diacriticals, then you can do fun things like enable ODBC tracing and open a PMR. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
