| Author |
Message
|
| Inforz |
 Posted: Thu May 05, 2011 6:56 am Post subject: Cluster v7 problems |
 |
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
I was running MQ in v6 in which due some probs I deleted (the one and only) full repos QM and recreated it. As a result there were two QMs with same name (and different QMIDs).
So i gave reset cluster for the old qmid. And then issed refresh cluster(<clus name>) repos(yes) on all partial repositories(5 PRs). and issued refresh cluster(<clus name>) in the only full repos. I was able to see all the cluster QMs in the full repos when I issed dis clusqmgr(*). But in PRs I was able to see only that QM and Full Repos in it. The other PRs were not displayed.
Then I migrated MQ from 6.0.0.10 to 7.0.1.3(as I was forced to). And now too, the same prob. All the cluster channels are in running state with NO SYSTEM.TEMPQMGR.xxx states while displaying clus qmgrs.
I need all the clus qmgrs to be displayed in all the clus qmgrs.
 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu May 05, 2011 7:01 am Post subject: Re: Cluster v7 problems |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Inforz wrote: |
| I was running MQ in v6 in which due some probs I deleted (the one and only) full repos QM and recreated it. As a result there were two QMs with same name (and different QMIDs). |
So let's be clear here:
- you had a cluster with only one FR not the 2 required
- you deleted it without removing it from the cluster first
- you then added an identically named queue manager back into the cluster without first removing the reference your ill-judged action had left hanging
| Inforz wrote: |
| So i gave reset cluster for the old qmid. And then issed refresh cluster(<clus name>) repos(yes) on all partial repositories(5 PRs). and issued refresh cluster(<clus name>) in the only full repos. I was able to see all the cluster QMs in the full repos when I issed dis clusqmgr(*). But in PRs I was able to see only that QM and Full Repos in it. The other PRs were not displayed. |
So having typed some commands (how did you arrive at that sequence?) your cluster (which still only has 1 FR & is therefore not right) remained hosed.
| Inforz wrote: |
| Then I migrated MQ from 6.0.0.10 to 7.0.1.3(as I was forced to). And now too, the same prob. All the cluster channels are in running state with NO SYSTEM.TEMPQMGR.xxx states while displaying clus qmgrs. |
So when you migrated the broken cluster from WMQv6 to WMQv7 it remained broken? And you're surprised?
| Inforz wrote: |
| I need all the clus qmgrs to be displayed in all the clus qmgrs. |
What you need is the cluster to be correctly configured. Remove all the queue managers from it & redefine it. With 2 FRs.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 05, 2011 7:02 am Post subject: Re: Cluster v7 problems |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Inforz wrote: |
| I need all the clus qmgrs to be displayed in all the clus qmgrs. |
Note also that even when you get the cluster working this will never happen. It's not how WMQ clusters work. Only the FRs display all the queue managers. Check the Clusters docuementation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Inforz |
| Posted: Thu May 05, 2011 6:55 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Your assumptions are right.
I said ""NO"" TEMPQMGRs are displayed in a dis clusqmgr(*) output of all qm.s and no surprises.
As per a similar PMR, this could be achieved once there are communications between PRs.
And before deleting QMs, I need to take a backup(only QM and its OBJs and not its msgs) for which I guess saveqmgr util is not sufficient. Are there any alternatives for taking QM backup? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 05, 2011 7:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you want to be able to recreate a qmgr you will need 2 things:
- a backup done with saveqmgr (MS03) (thanks Wayne and Jeff) for the queues and authorizations
- a copy of qm.ini as it will have the other information you need to rebuild
As you noted this will not save any messages.
As an alternative you could stop the qmgr and make a full file system backup...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 06, 2011 4:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Inforz wrote: |
| I need to take a backup(only QM and its OBJs and not its msgs) for which I guess saveqmgr util is not sufficient. |
Why would you guess that something called "saveqmgr" wouldn't be sufficient to save a queue manager?
Why guess at all when you can look at the support pac and see what it does?
Why are you bringing the same combination of guesswork and random action to the removal of the cluster as you seem to have brought to it's creation?
A wise man once nearly said:
"You cannot solve a problem with the same kind of thinking that caused it"
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 06, 2011 4:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Except that saveqmgr does not actually backup the queue manager, merely the objects defined to it.
So the "restored" queue manager will have a different QMID than the old qmgr. Which will mean that the cluster does not see it as "the same" qmgr at all.
If you have a cluster that does not have any working FRs, first promote a PR to being a new FR. Then delete the entire cluster, from the outside in (unshare all queues, remove all PRs, then remove the FR). |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri May 06, 2011 5:12 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If you are responsible for an MQ cluster, you should have MQ Admin test queues defined on each QM in the cluster, with a little script that connects to each QM and tests putting messages from each QM to every other QM. By running this script, you prove all your cluster QMs are talking with each other anytime you need to verify connectivity. If you create the queues and script correctly, you can also use this to test the load balancing and likely learn quite a bit on how MQ clustering works.
My script is just a plain Windows .bat file that calls amqsputc over and over.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Inforz |
| Posted: Mon May 09, 2011 6:52 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
| Thanks Peter. Thats a handy tip. |
|
| Back to top |
|
|
|
|
