Author |
Message
|
BBM |
Posted: Mon Jun 29, 2009 6:39 am Post subject: Problems failing over MQ 6.0.2.3 on MSCS cluster |
|
|
Master
Joined: 10 Nov 2005 Posts: 217 Location: London, UK
|
Hi,
We're having issues failing over a newly created MSCS cluster queue manager.
We're using Windows 2000 Server SP4 with MQ 6.0.2.3.
Each time I create a queue manager on either node of the cluster and fail it to the other node the queue manager data does not get copied to the other nodes registry and we get the following error:
"Could not locate mangled QM in registry"
Shortly aftwerwards the cluster group fails and moves back to the original node where it runs happily.
I've looked at disk permissions for the shared disk and everything looks fine..
Any suggestions?
Thanks
BBM |
|
Back to top |
|
 |
exerk |
Posted: Mon Jun 29, 2009 7:46 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Have you followed the MSCS section in the System Administration Guide? Have you migrated the queue manager created to MSCS control? From your description, it sounds like you have not done so, but happy to stand corrected. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
BBM |
Posted: Tue Jun 30, 2009 12:09 am Post subject: |
|
|
Master
Joined: 10 Nov 2005 Posts: 217 Location: London, UK
|
Hi,
Yes I have followed the instructions in the system admin manual.
We have around 40 MSCS clusters with queue managers that I have created over the past four years.
This is why I am so puzzled with this issue.
Thanks
BBM |
|
Back to top |
|
 |
vol |
Posted: Tue Jun 30, 2009 3:45 am Post subject: |
|
|
Acolyte
Joined: 01 Feb 2009 Posts: 69
|
The phrase "mangled QM" refers to the QM name being transformed if it contains certain characters. The only one I know for sure is that . (full stop) is changed to ! (exclamation mark). If your qmgr name contains any characters other than A-Z, a-z, 0-9 then this may be causing the problem. I would have thought that if so it is almost certainly an APARable problem, so you should get a fix (Asterix!) from IBM. |
|
Back to top |
|
 |
ramires |
Posted: Tue Jun 30, 2009 5:44 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001 Posts: 523 Location: Portugal - Lisboa
|
you can compare registry entries in both nodes and also the working directories the queue manager uses, to find differences |
|
Back to top |
|
 |
aditya.aggarwal |
Posted: Tue Jul 07, 2009 5:34 am Post subject: |
|
|
 Master
Joined: 13 Jan 2009 Posts: 252
|
It seems to be Windows 2000 problem... Ask your windows adminstrator to raise ticket with microsft to get a comment on this...
Cheers,
Aditya |
|
Back to top |
|
 |
|