| Author |
Message
|
| torr_chula |
 Posted: Mon Nov 13, 2006 4:38 am Post subject: Problem about inserting, querying Thai characters with DB2 |
 |
|
Novice
Joined: 07 Nov 2006
Posts: 12
|
1. When sending messages contain Thai characters to Message Broker and then insert them into DB2 by Message Broker, Thai characters cannot be read in DB2 Control Center (1 Thai character in the message -> 3 unreadable characters in DB2).
2. When trying to insert Thai characters by DB2 Control Center and let Message Broker read it, an error occur as following :
Nov 13 06:07:44 seaibrt1 user:err|error WebSphere Broker v6002[385140]: (EAI_BK01.SAP_INBOUND_EXG)[3145]BIP2488E:
(.ReadThaiDataFromDB_Compute.Main, 9.3) Error detected whilst executing the SQL statement 'SET
Environment.Variables.QueryResult = THE (SELECT COLUMN(0) AS :VALUE FROM DATABASE());'. :
EAI_BK01.eba321c6-0d01-0000-0080-cdc8bde5a00c:
/build/S600_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp: 589: SqlStatementGroup::execute:
ComIbmComputeNode: ReadThaiDataFromDB#FCMComposite_1_3
Nov 13 06:07:44 seaibrt1 user:err|error WebSphere Broker v6002[385140]: (EAI_BK01.SAP_INBOUND_EXG)[3145]BIP2135E:
Source character 'b7' in field '54657374e4b7c2' cannot be converted to unicode from codepage '1208'. :
EAI_BK01.eba321c6-0d01-0000-0080-cdc8bde5a00c: /build/S600_P/src/CommonServices/ImbConverter.cpp: 516:
ImbConverterCPP::internalToUnicode: :
Environments & Configuration
Broker Server :
AIX 5.3 ML2
WebSphere Message Broker V6.0.2.0
WebSphere MQ V6.0.1.1
DB2 Client V8.2 (64bit Instance)
IBM SDK 1.4.2
DB2 Server :
AIX 5.3 ML2
DB2 UDB V8.2 (64bit Instance)
IBM SDK 1.4.2
DB2 Script & Configuration :
CREATE DATABASE BRK_DB64 ON '/usr/opt/db2_08_01/brokerdata64' USING CODESET TIS620-1 TERRITORY TH
db2set db2codepage=874 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Nov 13, 2006 4:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Obvious question - are you sure the codepage conversions are properly installed?
Can you also confirm what the default codepages are? Looks like the queue manager is on 1208 & DB2 is on 874, but what is native for AIX?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| torr_chula |
| Posted: Mon Nov 13, 2006 4:57 am Post subject: |
|
|
Novice
Joined: 07 Nov 2006
Posts: 12
|
At this time, I can answer you only one question. The CCSID of the queue manager is 874. I've to check with my system engineer for codepage conversions and native for AIX and will tell you no later than tomorrow. Thanks you for your kindly help..  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 13, 2006 5:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Make sure that there is a LANG environment variable properly set and scoped in both the DB2 profile and the Broker profile, and then restart everything.
If the LANG (or NLS_LANG or a few other varients) is not set, then data doesn't get marked as being in the right codepage in the database.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| torr_chula |
| Posted: Tue Nov 14, 2006 3:46 am Post subject: |
|
|
Novice
Joined: 07 Nov 2006
Posts: 12
|
| Thanks everyone. This issue can be now solved on my development machine (Windows) by running the command "db2set DB2CODEPAGE=1208". I'll let my system engineer test on AIX soon. |
|
| Back to top |
|
|
| nheng |
| Posted: Sun Jun 07, 2009 7:13 pm Post subject: Another way to resolve |
|
|
Apprentice
Joined: 07 Dec 2007
Posts: 39
|
| torr_chula wrote: |
| Thanks everyone. This issue can be now solved on my development machine (Windows) by running the command "db2set DB2CODEPAGE=1208". I'll let my system engineer test on AIX soon. |
Someone has another way to resolve this problem.I can't change codepage of database.Please help.
Thanks. |
|
| Back to top |
|
|
|
|
