Author |
Message
|
RichA |
Posted: Mon May 01, 2006 10:48 pm Post subject: Broker Codepage Problem |
|
|
 Centurion
Joined: 14 Mar 2002 Posts: 102
|
When running commands on a linux broker we've recently started getting errors as below -
mqsilist BRK01
BIP2135E: Source character 'c6' in field 'c6600a00' cannot be converted to unicode from codepage '1208'.
The source character is an invalid code point within the given codepage.
Correct the application that generated the message.
BIP8081E: An error occurred while processing the command.
An error has occurred while the command was running. The command has cleaned up and terminated.
Use messages prior to this one to determine the cause of the error. Correct the problem and retry the command. Check for some common problems :- Is your userid in the mqbrkrs group ? Is the broker database working ? Is any operating system limit set too low to allow the command to run ? Is the environment correctly setup? Contact your IBM support center if you are unable to resolve the problem.
Has anyone seen this before? |
|
Back to top |
|
 |
Kateel |
Posted: Tue May 02, 2006 5:11 am Post subject: |
|
|
Novice
Joined: 01 May 2006 Posts: 17
|
I haven't seen the exact error.
But I guess you can try changing the ccsid to 1208 using alter qmgr command. |
|
Back to top |
|
 |
msukup |
Posted: Tue May 02, 2006 6:05 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2002 Posts: 56
|
Rich,
We had this same problem when performing db operations against a db where unicode was not supported. We opened a PMR, and IBM support instructed us to do the following:
Set variable
MQSI_LOCAL_CCSID=819 (or whatever codepage of broker is)
in .profile or system variables. Then restart broker. This will instruct broker to use its local codepage rather than unicode.
-Meredyth |
|
Back to top |
|
 |
RichA |
Posted: Tue May 02, 2006 10:10 pm Post subject: |
|
|
 Centurion
Joined: 14 Mar 2002 Posts: 102
|
Thanks for the replies, it turns out there was some file corruption on the SAN and we ended up having to recreate the broker, database and all.
I'm curious as to whether the set variable MQSI_LOCAL_CCSID=819 would have worked around the issues with the SAN though. |
|
Back to top |
|
 |
vennela |
Posted: Wed May 03, 2006 10:22 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
RichA wrote: |
I'm curious as to whether the set variable MQSI_LOCAL_CCSID=819 would have worked around the issues with the SAN though. |
I don't think so. Most likely all the language files and message catalog files might have got corrupted because of the disk. |
|
Back to top |
|
 |
|