| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Full Repository Queue Manager repository update |
« View previous topic :: View next topic » |
| Author |
Message
|
| PaulHuang |
 Posted: Tue Oct 16, 2001 6:49 am Post subject: |
 |
|
Novice
Joined: 31 Jul 2001
Posts: 18
|
hi
I have two full repository queue managers interconnected with explicit cluster sender/receiver channels defined. If one of the repository queue manager is not updated how and when will this repository queue manager request for repository update from the other queue manager? I am aware REFRESH is not recommended to use if necessary? Does this command suitable for this situation?
thanks for help! |
|
| Back to top |
|
 |
| bduncan |
| Posted: Tue Oct 16, 2001 2:03 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Paul,
Typically if one of the full repositories doesn't get an update to the cluster from the other full repository, let's say because of a network problem, then when network connectivity is reestablished, the update should flow automatically. This is because the update messages will queue up on the SYSTEM.CLUSTER.TRANSMIT.QUEUE, and wait for the channel to become active again.
If for some reason the repositories appear to be communicating with each other, but they still seem out of sync, you can issue a REFRESH CLUSTER command. This works equally well on non-repository machines that are members of the cluster. It basically forces the queue manager to re-resolve all the cluster objects and this will get your repositories back in sync...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| PaulHuang |
| Posted: Wed Oct 17, 2001 1:14 am Post subject: |
|
|
Novice
Joined: 31 Jul 2001
Posts: 18
|
hi Brandon
Thanks for the reply! Is there any side effect of using refresh command ? It is advised to be used if neccessary in the redbook and also after browsing several pmrs in retain saying use of refresh may confuse the cluster network or even damage it?
I have the following situation and hope for any sights:
Two interconnected full repository queue manager say A and B. They work fine until a removal of queue manager B without following the procedure described in the redbook. The queue manager B is recreated again and trying to rejoin back to the same configuration. but have found from queue manager B runmqsc:
Cluster qmgr list
display clusqmgr(*)
36 : display clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(B) CLUSTER(AB)
CHANNEL(TO.B)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(SYSTEM.TEMPQMGR.a(1415))
CLUSTER(AB) CHANNEL(TO.A)
display chstatus(*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.A) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(a's ipaddress) CURRENT
CHLTYPE(CLUSSDR) STATUS(RUNNING)
but have no TO.B channel up and running.
the error log for queue manager B also shows:
Error LOG:
10/15/01 13:39:37
AMQ9419: No cluster-receiver channels for cluster 'AB'
EXPLANATION:
The repository manager has received information about a cluster for which no
cluster-receiver channels are known.
ACTION:
Define cluster-receiver channels for the cluster on the local queue manager.
Why there will be a SYSTEM.TEMPQMGR.a(1415) clusqmgr showing up?
do you have any idea what can be done to make it work again?
thanks |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Oct 17, 2001 5:53 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Paul,
Your problem here is that your new queue manager B is not the same as the old queue manager B. Part of the information that is kept, for clustering, about a QM is it's creation date/time.
So when A tries to talk to B, it's still looking for the old B. And when B tries to talk to A, A thinks it's an 'imposter'.
If it isn't too dificult, your best bet here would be to start from scratch again. Sorry.
Cheers.
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
