| Author |
Message
|
| Erik |
 Posted: Sat Apr 03, 2004 4:11 am Post subject: CCSID problem in mscs clustered environment |
 |
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi all,
I installing a mscs Cluster with
w2k adv server
MQ5.3 csd 4
WMQI 2.1 csd 5
DB2 7.2
I am using the ih03 support pack to do the testing, and using the rfhutil.exe to check the messages.
In Node1 all is working just fine and test messages sent passes through
and are stopped at xmitq.
These messages all have code page 1252 in the mqmd tab when I browse the messages.
In node 2 all messages fail. All messages goes to a error queue.
And when I look at the code page the all have 437 as value.
I did a alter qmgr ccsid(1252) after installing the queuemanager
(in node 1)
But it seems like node 2 is not picking up the change...
I checked node 2 did the dis qmgr and the ccsid IS 1252
but I still get the same fault: all failing messages comes from node 2
and all failing messages have code page 437.
I have tried to do the alter qmgr ccsid(1252) in node 2 but the result is still the same.
Does anyone have a clue how to fix this or atleast point me in some direction?
Please advice
Erik
_________________
Erik |
|
| Back to top |
|
 |
| kman |
| Posted: Mon Apr 05, 2004 12:22 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
shouldn't the codepage on windows be 437? mm  |
|
| Back to top |
|
|
| Erik |
| Posted: Mon Apr 05, 2004 12:29 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
The cust. requieres CCSID to be 1252 because they are handling several european clients (with all the special characters).
_________________
Erik |
|
| Back to top |
|
|
| kman |
| Posted: Mon Apr 05, 2004 12:33 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
sorry, I overlooked the requirement. As long as it is a supported codepage.
Is there anything glaring in the amqerr01.log about the error? Is there any FDC created? If so, please quote or code the header part of the FDC. |
|
| Back to top |
|
|
| Erik |
| Posted: Mon Apr 05, 2004 1:02 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi again,
Checking the registry shows a difference in the codepage.
Node 1
ACP 1252
OEMCP 850
Node 2
ACP 1252
OEMCP 437
I have no idea what this means, but these should be the same because both machines in the cluster are supposed to be configured the same way.
I have limited access to problem machine rigth now..will post the error log and FDC asap..
Best regards
Erik |
|
| Back to top |
|
|
| Erik |
| Posted: Mon Apr 05, 2004 4:23 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi all,
The FDC
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon April 05 13:38:30 Romance Daylight Time 2004 |
| Host Name :- ANTNTBP12 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.4 CSD04 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MC008044 |
| Application Name :- MQM |
| Component :- MQMDoTerminate |
| Build Date :- Jun 18 2003 |
| CMVC level :- p530-04-030617 |
| Build Type :- IKAP - (Production) |
| UserID :- clustersvc |
| Process Name :- C:\WINNT\cluster\resrcmon.exe |
| Process :- 00001804 |
| Thread :- 00001800 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (***CMQMException Caught***: Unable to initialize COM libraries, status: |
| 0) |
| FDCSequenceNumber :- 0 |
| Comment1 :- ***CMQMException Caught***: Unable to initialize COM |
| libraries, |
| |
+-----------------------------------------------------------------------------+
No MQM Function Stack Available
AMQERRORLOG
04/05/2004 10:43:34
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1808.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 668 --------------------------------------------------------
04/05/2004 13:38:29
AMQ6119: An internal WebSphere MQ error has occurred (***CMQMException
Caught***: Unable to initialize COM libraries, status: 0)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 628 --------------------------------------------------------
04/05/2004 13:38:30
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1804.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 668 --------------------------------------------------------
_________________
Erik |
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Apr 05, 2004 5:01 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Are you sure these 2 problems are related? Ie do you get a new fdc everytime you get the ccsid error?
For the dcom error:Look in the system event logs of the node where the FDC is generated. Any COM or DCOM events logged at that point in time?
Make sure you tick the box 'Run in seperate resource monitor' as it prevents others from interfering with MQ's resource. I assume you have set up the MQ as an MSCS resource and it was working before you tried to add the MQSI on top of it?
(Make sure clustersvc is a member of the local mqm group on both nodes as well) |
|
| Back to top |
|
|
| Erik |
| Posted: Mon Apr 05, 2004 5:50 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi again,
The FDC and errorlog coinsides with one test run.
There is not a fdc file created for every test run.
There is no DCOM or COM error in the system event log on the failing node.
Yes MQ was running fine before I put the MQSI in, actually MQSI was running well when I used test flows that didn't care about CCSID.
The actual flows do care since it must be able to cope with german "umlauts" and other special european characters.
clustersvc is a member of the local mqm group on both nodes
_________________
Erik |
|
| Back to top |
|
|
| Erik |
| Posted: Thu Apr 08, 2004 12:49 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi all, This problem have now been resolved.
It didn't have anything to do with the CCSID after all, when a message enter the error flow it picks up the native CCSID 437 ...
Problem was one of 3 databases didn't connect properly on second node.
Best regards
Erik |
|
| Back to top |
|
|
|
|
