| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ Cluster auto defined channels |
« View previous topic :: View next topic » |
| Author |
Message
|
| MQ_Lover |
 Posted: Fri Nov 08, 2013 4:19 am Post subject: |
 |
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Rammer - I have done a RESET cluster on one of the full repositories and now see that broken Queue Manager reference is no more there means on DIS CLUSQMGR it says below
CSQO030I No objects of type CLUSQMGR match QMGRNAME.
And looks good on all Full Repositories.
But on the Windows Queue Manager still the auto-defined CLUSSDR channels are in RETRYING state, how do I get rid off them any idea?
This is what is still there as of now in Windows Queue Manager
I have ***** out the real names
dis clusqmgr(*)
9 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(*****) CHANNEL(******)
CLUSTER(CLUS)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(*****) CHANNEL(*******)
CLUSTER(CLUS)
dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(******) CHLTYPE(CLUSSDR)
CONNAME(******(2305)) CURRENT
RQMNAME( ) STATUS(RETRYING)
SUBSTATE( ) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8417: Display Channel Status details.
CHANNEL(******) CHLTYPE(CLUSSDR)
CONNAME(******(2205)) CURRENT
RQMNAME( ) STATUS(RETRYING)
SUBSTATE( ) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE) |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Nov 09, 2013 1:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
you may need to remove from the SCTQ all messages to a clustered destination, before you can get rid of the cluster information... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rammer |
| Posted: Sun Nov 10, 2013 2:05 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Have you tried, stopping the channels, or stop / starting the Queue Manager to see if that clears them out.
If it doesnot then you may need to clear the messages off the SCTQ.
Also on the windows Queue Manager what is the output of
DISC CLUSQMR(*)
And I think you said earlier you deleted the defined cluster / sender channels? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Nov 10, 2013 6:28 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
| MQ_Lover wrote: |
But on the Windows Queue Manager still the auto-defined CLUSSDR channels are in RETRYING state, how do I get rid off them any idea?
|
You want to remove the Windows QM from the cluster, but it still shows automatic cluster channels?
Follow the steps to properly remove a QM from a cluster:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzah.doc/qc12130_.htm
In particular, pay attention to Step 8.
| Quote: |
| Issue the REFRESH CLUSTER command on TORONTO queue manager to remove any auto-defined cluster channels. |
Don't run off and run that command. Read the whole article and make sure you do all the steps that apply first, then issue the refresh command to purge any auto cluster channels.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Nov 12, 2013 6:00 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1230
Location: Gold Coast of Florida, USA
|
In the future when a Qmgr cannot resolve a host name in the DNS for whatever reason, you should add that host name and IP to your /etc/hosts file which may be at C:\Windows\System32\drivers\etc\hosts in Windows.
You should never put the IP address in the CONNAME as that address is sure to change one day.
On the 3 FR issue if you insist in having more than two FRs, ensure each FR has an explicit cluster sender to all other FRs (in your case two). This is because an FR will only forward cluster updates to other FRs to which it has an explicit cluster sender channel.
If you find that you did not have explicit cluster senders at each FR to all other FRs, then you can be sure you have a fragmented cluster. What is the resolution? Well, you could demote all but one FR to PRs and refresh those with a REPOS(YES) and promote them back to FRs. Or you can issue REFRESH CLUSTER(...) REPOS(YES) at each and every PR (once you have corrected your FR cluster senders).
Of course, you could just correct the FRs cluster senders and only refresh cluster as you come across issues... Which will dog you forever. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
