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 » Refresh Cluster

Post new topic  Reply to topic
 Refresh Cluster « View previous topic :: View next topic » 
Author Message
rammer
PostPosted: Fri Jan 18, 2013 10:55 am    Post subject: Refresh Cluster Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

Hi All.

I had to rebuild a quuee manager that was a partial repository to use larger log files as we were unable to increase the volume being used any further.

The following is what I carried out on the partial
Backed up the queue manager with save queue manager

Suspended the Queue Manager, and this showed suspended on the FullReposistories

Alter the ClusRcvr to have no entry in the cluster setting

Stopped the Clusrcvr and deleted it

Stopped the Cluster Sender and deleted that as well.

Stopped Queue Manager, deleted it and rebuilt it using larger logs, then piped in the saveqmgr definitions.

On checking the rebuilt queue manager it joined the repository without issue all channels were running and when doing a dis clusqmgr(*) it showed no TempQeueManagers.

Any messages put to the newly built queue manager via the cluster are working fine.

MY query is
On the full repository and also other members of the cluster when issuing dis qc(TEST.NEWQUEUEMANAGER.Q) it shows an entry for the previous build of the queue manager (old QMID) and the newly built one.

As mentioned this is not causing a problem at the moment but in the past I have seen that it has.

Do you guys recommend issuing a REFRESH for the cluster and if so on which ones? If I do it against a full repos I believe it just goes and gets the information from the other full repos?

Any usefull advice is appreciated
Thanks

Ps Queue Manager is Version 6 and full repos is 7. We will be upgrading shortly, this is only test environment as well.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Jan 18, 2013 11:07 am    Post subject: Reply with quote

Poobah

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

Cluster entries for qmgrs no longer present in the cluster should not create a problem, and can be ignored. They will stale-out in 61 days (if memory serves) and be purged automatically.
_________________
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
rammer
PostPosted: Fri Jan 18, 2013 11:18 am    Post subject: Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

Fingers crossed.. Thanks
Back to top
View user's profile Send private message
mvic
PostPosted: Fri Jan 18, 2013 4:37 pm    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

rammer wrote:
Fingers crossed.. Thanks

Maybe this helps: http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.doc/qc13260_.htm
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Refresh Cluster
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.