| Author |
Message
|
| PeterPotkay |
 Posted: Thu Mar 18, 2010 12:44 pm Post subject: Moving a Full Repository |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I am moving one of my 2 Full Repositories from 1 QM to another, and using the instructions in the Clusters manual.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzah.doc/qc11660_.htm
Task 6 has us cleaning up the manually defined CLUSSNDR from the FR that is not changing (New York) to the old FR that is now a PR (London). But I ran into a problem. When I go to NewYork to delete the CLUSSNDR to London, I can't because it is still running. London is still an active member of the cluster. So I stopped the channel. That allowed me to delete it. But then NewYork was never able to send anything to London, even though it knew everything about London. If I added a new queue to London, New York knew about it. Yet any messages to London just sat in New York's S.C.T.Q, and New York did not consider London a valid destination for round robining.
If I do a Channel Status list, there are no stopped, inactive, retrying, etc channels from New York to London.
In MO71 I did a Cluster Queue Manager list for all QMs, all channels on New York. In that output I saw that the channel from New York to London was stopped. I started it thru that interface and now all appears well.
What did I do wrong, or is this the only way? Because the communications between New York and London are very busy, it maybe months before that channel ever goes Inactive and allows me to delete it. Otherwise I feel I have to manually stop it to delete it, then manually start it thru the Cluster Queue Manager list since that's the only place I see it stopped.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| mvic |
| Posted: Thu Mar 18, 2010 2:58 pm Post subject: Re: Moving a Full Repository |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| PeterPotkay wrote: |
Yet any messages to London just sat in New York's S.C.T.Q, and New York did not consider London a valid destination for round robining.
If I do a Channel Status list, there are no stopped, inactive, retrying, etc channels from New York to London. |
If London-bound msgs were sitting in NY's SCTQ they must have been identified by the qmgr as destined for London. This problem sounds like a failure to start a channel, or identify that a channel needed to be started.
I don't expect you had to start the channel from MO71 - runmqsc or Explorer etc. etc. should have worked as well.
I can't remember, but if you STOP a channel, isn't that taken by the qmgr as an instruction to leave it stopped until later manual intervention? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Mar 18, 2010 5:08 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I've never tried to start a channel that wasn't defined or that didn't show up in a channel status list of all channels, but apparently the QM still has some record of me requesting to stop it, and so new messages in the SCTQ sit.
Doing a cluster queue manager list (I use MO71, but runmqsc or Explorer should show it to), I was able to identify this stopped instance. Starting it got everything back in order.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 18, 2010 8:46 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
I've never tried to start a channel that wasn't defined or that didn't show up in a channel status list of all channels, but apparently the QM still has some record of me requesting to stop it, and so new messages in the SCTQ sit.
Doing a cluster queue manager list (I use MO71, but runmqsc or Explorer should show it to), I was able to identify this stopped instance. Starting it got everything back in order. |
What happened is that stopping the channel manually both stopped the manual defined one and the self defined one.
As you found out after removing the manual defined one you still have to start the self defined one. It would / should have showed up as stopped in the MO71 channel status.
You can start an autodefined cluster channel receiver in MO72 from the command line. The channel need not exist and not appear in the local qmgr's channel list or in its status list... It may need however to show up in the clusqmgr display => the local qmgr knows about it.
I usually try to start a cluster sender that way if it does not start on its own. Sometimes a cluster refresh is needed when one FR does not catch up on the information from the other FR. (Maybe it's me just being too impatient  )
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Mar 19, 2010 3:58 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| fjb_saper wrote: |
As you found out after removing the manual defined one you still have to start the self defined one. It would / should have showed up as stopped in the MO71 channel status.
|
It did not, even though I was asking for channel status for all channels. That's what threw me. I'll verify the next environment I do this on, but 2 so far are consistent. I'll see what runmqsc shows for channel status after I stop the channel, and after I delete the channel. If you delete a stopped channel MQ clears it out of the channel status list. And that's a problem in this scenario. Good thing Cluster Queue Manager List still showed it to provide a clue, although I bet if I just issue a runmqsc command to start TO.LONDON even though the channel is no longer defined and its no longer in the Channel Status list table it will work.
I submitted feedback to that topic in the Info Center asking them to consider what we have to do if the channel is running and to add those extra steps.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 19, 2010 6:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
An other alternative would probably be to do a refresh cluster on the new PR. This should however only be necessary if the FR no longer has the reference to the PR, after the channel was deleted.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Mar 20, 2010 4:00 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Actually I did try that. Didn't work. But I did see the S.C.T.Q. on the FR back way up as the FR tried to talk with the PR due to the PR's refresh request. But the stopped channel blocked it.
I wonder if refreshing the FR would have worked. Not that that is a good option in light of the fact that simply starting the channel directly worked.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 20, 2010 7:20 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
Actually I did try that. Didn't work. But I did see the S.C.T.Q. on the FR back way up as the FR tried to talk with the PR due to the PR's refresh request. But the stopped channel blocked it.
I wonder if refreshing the FR would have worked. Not that that is a good option in light of the fact that simply starting the channel directly worked. |
As long as the PR is correctly referenced in the FR nothing else but manually starting the channel and troubleshooting any cause that prevents the channel to run will do.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Mar 21, 2010 5:50 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Not good. The New York and London QMs were restarted last night, and this morning the problem is back. Cluster Queue Manager list shows the channel from New York to London stopped, and it does not show any status in a regular channel status listing. Messages destined for London are backing up in the New York S.C.T.Q.
This time I got it going by issuing
| Code: |
| start channel(TO.LONDON) |
from a runmqsc session on New York. Maybe New York will remember this time?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 21, 2010 7:23 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
Not good. The New York and London QMs were restarted last night, and this morning the problem is back. Cluster Queue Manager list shows the channel from New York to London stopped, and it does not show any status in a regular channel status listing. Messages destined for London are backing up in the New York S.C.T.Q.
This time I got it going by issuing
| Code: |
| start channel(TO.LONDON) |
from a runmqsc session on New York. Maybe New York will remember this time? |
Did you check if any of the qmgrs was suspended? On FR execute
dis clusqmgr(*) where (suspend eq yes)
Depending on how the suspend command is issued (mode) it will stop the cluster receiver. Typically I would expect the autodefined sender to go into retry... Check timing of short and long retrys... maybe too short for recovery??? So you'd need to do a manual start of autodefined senders??
[edit]Do all your target qmgrs have a DLQ? Could it be that the channels stops because a target queue is full? By the time you get to look at it the target queue has room again? Although I would expect this to be caught by monitoring...[/edit]
_________________
MQ & Broker admin
Last edited by fjb_saper on Sun Mar 21, 2010 10:31 am; edited 1 time in total |
|
| Back to top |
|
|
| mvic |
| Posted: Sun Mar 21, 2010 8:59 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| PeterPotkay wrote: |
| Cluster Queue Manager list shows the channel from New York to London stopped, and it does not show any status in a regular channel status listing. Messages destined for London are backing up in the New York S.C.T.Q. |
Trace + PMR? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Mar 21, 2010 12:56 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
FJ,
None are suspended. The channel starts up fine when manually told to. It never went to retry. DLQs properly defined everywhere. I'm hoping what I did this A.M. did it for good. I just put the channel into stopped mode (Inactive) and it started back up on its own when it had work to do. I restarted the NewYork QM and again, the channel worked as expected.
Maybe the explicit start channel command via runmqsc did something better than what I did the first night when I restarted the channel via the Cluster Queue Manager List in MO71.
mvic,
I have 5 weeks before I have to do the QA environment. Any more problems with this channel and it will be PMR time.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 21, 2010 6:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
Maybe the explicit start channel command via runmqsc did something better than what I did the first night when I restarted the channel via the Cluster Queue Manager List in MO71. |
Strange... I never use that. I either use a channel status window or MQSC window (MO71) or use runmqsc or MO72 to start the autodefined channel...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
