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 » Messages in clus.xmit.q for qmgr that doesn't exist

Post new topic  Reply to topic
 Messages in clus.xmit.q for qmgr that doesn't exist « View previous topic :: View next topic » 
Author Message
Boomn4x4
PostPosted: Wed Dec 05, 2012 5:45 am    Post subject: Messages in clus.xmit.q for qmgr that doesn't exist Reply with quote

Disciple

Joined: 28 Nov 2011
Posts: 172

I found the sys.clus.xmit.q backed up for one of my qmgrs. The messages are looking for a qmgr that no longer exists. I think it is safe to assume that I can clear those messages from the queue.... my question is, how?

I suppose I could just do a clear messages from the Explorer, or I could run the amqsget0 application, but that would clear all of the messages on the queue.. however, if there were messages enroute to other qmgrs, those would be removed also. Is there a way I can get the messages off that queue without being so destructive??? Short of writing an application to do so?
Back to top
View user's profile Send private message
nathanw
PostPosted: Wed Dec 05, 2012 6:14 am    Post subject: Reply with quote

Knight

Joined: 14 Jul 2004
Posts: 550

what numbers are we talking about?

if the number is low then simply use rfhutil

there are several apps out there from sponsors of this site and as support pacs from IBM try looking through
_________________
Who is General Failure and why is he reading my hard drive?

Artificial Intelligence stands no chance against Natural Stupidity.

Only the User Trace Speaks The Truth
Back to top
View user's profile Send private message MSN Messenger
Boomn4x4
PostPosted: Wed Dec 05, 2012 6:29 am    Post subject: Reply with quote

Disciple

Joined: 28 Nov 2011
Posts: 172

Almost 800 messages.
Back to top
View user's profile Send private message
exerk
PostPosted: Wed Dec 05, 2012 7:21 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

MO71 (if you can use it) is ideal for the job...
_________________
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
View user's profile Send private message
Boomn4x4
PostPosted: Fri Dec 07, 2012 6:31 am    Post subject: Reply with quote

Disciple

Joined: 28 Nov 2011
Posts: 172

Along these same lines.... how do I keep the queue manager from trying to send to this now non-existent queue manager? The error log is showing that its trying to connect to a sender channel, at a remote location that no longer exists. Since it is an auto sender channel, is there a way to delete it?
Back to top
View user's profile Send private message
exerk
PostPosted: Fri Dec 07, 2012 7:07 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Boomn4x4 wrote:
Along these same lines.... how do I keep the queue manager from trying to send to this now non-existent queue manager? The error log is showing that its trying to connect to a sender channel, at a remote location that no longer exists. Since it is an auto sender channel, is there a way to delete it?

Research the RESET CLUSTER command...
_________________
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
View user's profile Send private message
JosephGramig
PostPosted: Fri Dec 07, 2012 7:48 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA

Well, it depends...

If this is a Full Repository for the cluster that the missing QMGR is a part of, then RESET CLUSTER is the command you are looking for.

If this is not a Full Repository for the cluster that has the missing QMGR, then If and only IF, this QMGR can communicate with the Primary Full Repository (the one it has an explicit cluster sender channel to), REFRESH CLUSTER(...) REPOS(YES) is your answer and it should also clear the S.C.T.Q.

BTW, before you do any of this, make sure the FRs think the QMGR that should be gone also believe it is gone. Check them all!

You are out of sync with the FRs.

Finally, every FR for a CLUSTER must have an explicit cluster sender to every other FR in that cluster. An FR will only forward updates to those FRs that it has an explicit cluster sender to. This is why it is best practice to have two and only two FRs for any cluster and that they have explicit cluster senders to each other.
Back to top
View user's profile Send private message AIM Address
nareshm13
PostPosted: Fri Dec 07, 2012 7:27 pm    Post subject: Reply with quote

Apprentice

Joined: 07 Dec 2012
Posts: 29

Otherwise you can take the backup of the messages using q tool..!!
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Messages in clus.xmit.q for qmgr that doesn't exist
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.