ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » cluster resolution problem

Post new topic  Reply to topic Goto page Previous  1, 2
 cluster resolution problem « View previous topic :: View next topic » 
Author Message
cicsprog
PostPosted: Fri May 18, 2012 6:18 am    Post subject: Reply with quote

Partisan

Joined: 27 Jan 2002
Posts: 347

guy11 wrote:
cicsprog wrote:
+1

You may want to do a DIS CLUSQMGR(*) CLUSTER(<cluster name>) to see if the QMID and CLUSTER date and times match match between MQM's. If they don't you have corrupt repositories.


Thanks. QMID matches, but the CLUSDATE and CLUSTIME doesn't match for some of the clusters, so those cluster caches are corrupted is it ?.


This needs to be fixed. Make sure you have mutiple MQM's with the same names, same cluster, but mismatches on cluster date and times. You have a definite problem with subscription messages flowing to MQM's in the cluster. You'll need to issue the dreaded RESET to clean up the mismatches.

*****Newest entry****

Cluster queue manager name : WLSFRDT03A
Channel name . . . . . . . : TO.WLSFRDT03A.00
Disposition . . . . . . . . : - MQC2
Channel definition type . . : CLUSSDRA
Cluster name . . . . . . . : WHS/DEV

Queue manager identifier . : WLSFRDT03A_2012-05-16_16.17.51
Repository management . . . : N Y=Yes, N=No
Suspended . . . . . . . . . : N Y=Yes, N=No
Cluster workload rank . . . : 0 0 - 9
Cluster workload priority . : 0 0 - 9
Cluster workload weight . . : 50 1 - 99

Cluster time . . . . . . . : 2012-05-16 16.17.51 <====

*****Old entry****

Cluster queue manager name : WLSFRDT03A
Channel name . . . . . . . : TO.WLSFRDT03A.00
Disposition . . . . . . . . : - MQC2
Channel definition type . . : CLUSSDRA
Cluster name . . . . . . . : WHS/DEV

Queue manager identifier . : WLSFRDT03A_2011-10-31_12.14.31
Repository management . . . : N Y=Yes, N=No
Suspended . . . . . . . . . : N Y=Yes, N=No
Cluster workload rank . . . : 0 0 - 9
Cluster workload priority . : 0 0 - 9
Cluster workload weight . . : 50 1 - 99

Cluster time . . . . . . . : 2011-05-16 22.05.51 <=====

RESET CLUSTER(WHS/DEV) ACTION(FORCEREMOVE) +
QMID(WLSFRDT03A_2011-10-31_12.14.31)
Back to top
View user's profile Send private message
mvic
PostPosted: Fri May 18, 2012 6:41 am    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

cicsprog wrote:
You'll need to issue the dreaded RESET to clean up the mismatches.

Did you mean to say REFRESH?
Back to top
View user's profile Send private message
cicsprog
PostPosted: Fri May 18, 2012 6:45 am    Post subject: Reply with quote

Partisan

Joined: 27 Jan 2002
Posts: 347

mvic wrote:
cicsprog wrote:
You'll need to issue the dreaded RESET to clean up the mismatches.

Did you mean to say REFRESH?


Nope...this is after you have REFRESHed and still see the entry. I've seen this happen when a CLUSTER MQM has not been taken out of the CLUSTER properly via the documented removal process.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri May 18, 2012 7:47 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

What could possibly go wrong with REFRESH and RESET CLUSTER commands?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
cicsprog
PostPosted: Fri May 18, 2012 8:06 am    Post subject: Reply with quote

Partisan

Joined: 27 Jan 2002
Posts: 347

Yepper...dangerous commands....while the cluster feature has improved dramatically, it's still not wrapped too tight. Mostly self inflicted wounds though to be fair to IBM and their product.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri May 18, 2012 8:50 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

The WMQ Queue Manager Clusters manual is a must-read! And, oddly, ironically, seldom read, and less-often followed.

Yep. Resulting in self-inflicted wounds.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » Clustering » cluster resolution problem
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.