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 problem SYSTEM.TEMPQMGR.XXxXXX

Post new topic  Reply to topic
 Cluster problem SYSTEM.TEMPQMGR.XXxXXX « View previous topic :: View next topic » 
Author Message
dev135
PostPosted: Tue Oct 21, 2008 10:23 am    Post subject: Cluster problem SYSTEM.TEMPQMGR.XXxXXX Reply with quote

Apprentice

Joined: 21 Oct 2008
Posts: 44

I have a cluster namelist on server A QM, which is MQ 5.3 (aix server) and having a PR on Server B QM ,which is on MQ 6 (aix server)

Now when i display clusqmgr(*) on server B QM , i could not see server A name
and it displays SYSTEM.TEMPQMGR.XXxXXX instaed of Server A Queue Manager name.

Previously server B QM is on different host.
we removed queue manager on that host and created with same QM name of Server B on different host and had new clusrcvr defintions .

But on Server A , i still could see the automatically defined clussdr still shows conname of old hostname(portnumber).

how can i resolve this.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Tue Oct 21, 2008 11:07 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Check out the MQ Clustering Manual. In the trouble shooting section this scenario is talked about.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
dev135
PostPosted: Tue Oct 21, 2008 11:45 am    Post subject: Reply with quote

Apprentice

Joined: 21 Oct 2008
Posts: 44

Peter,

I checked in the cluster Manual and checked everything.


But on Server A , i still could see the automatically defined clussdr still shows conname of old hostname(portnumber).
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue Oct 21, 2008 12:37 pm    Post subject: Reply with quote

Poobah

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

Two approaches, both of which are from the WMQ Clusters manual.

The first approach would be to take the offending channel definition out of the cluster, correct (alter) the bad ipaddress(port) definition, then reintroduce the definition to the cluster. This is covered in the chapter on advanced tasks.

Another approach: same manual, the chapter on cluster commands:
REFRESH CLUSTER
You are unlikely to need to use this command, except in exceptional circumstances. Issue the REFRESH CLUSTER command from a queue manager to discard all locally held information about a cluster.
_________________
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
zhanghz
PostPosted: Thu Oct 23, 2008 10:45 pm    Post subject: Reply with quote

Disciple

Joined: 17 Jun 2008
Posts: 186

on the new QMGR B, you should be able to connect to A. Seeing SYSTEM.TEMPQMGR.* indicates B's CLUSSDR definition error, or network issue, I believe.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Oct 24, 2008 12:51 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

From what he is telling us this is due to 2 qmgrs with the same name in the FR. One with the old definition (qmgr is defunct) and one with the new definition. The channel from the full FR only accepts the old def.

Check out the cluster manual and specifically the command

reset cluster(mycluster) action(forceremove) ...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
zhanghz
PostPosted: Fri Oct 24, 2008 1:50 am    Post subject: Reply with quote

Disciple

Joined: 17 Jun 2008
Posts: 186

i understand A can still try to connect to old B, but that should not be the reason why the new B cannot see A. right?
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Oct 24, 2008 4:52 am    Post subject: Reply with quote

Poobah

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

Where I've seen this SYSTEM.TEMPQMGR.XXxXXX behavior the most: PR cluster qmgr has bad ipaddress(port) in its clusrcvr channel definition. When clussdr to FR is defined, the bad clusrcvr definition is sent to FR, and FR the bad definition cannot successfully be used by the FR to establish the FR-to-PR clussdrb channel.

Follow advanced tasks steps to remove the clusrcvr object from cluster, then correct the definition.
_________________
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 Page 1 of 1

MQSeries.net Forum Index » Clustering » Cluster problem SYSTEM.TEMPQMGR.XXxXXX
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.