| Author |
Message
|
| tsantoshkumar |
 Posted: Mon Apr 26, 2010 11:03 pm Post subject: MQ Cluster Sender Channel going into retrying state |
 |
|
Apprentice
Joined: 10 Mar 2008
Posts: 26
|
Hi,
Iam having a MQ cluster with 15 Queue Managers into the cluster. Recently due to some problem, we have shifted the Machine(full repository). I have taken the QManager backup and restored the same in new machine.
14 QM will be sending the files/data to our QM. After shifting to new machine , some of the QM(3) are not able to send the files properly. The cluster sender channel at remote is going into retrying mode.
As a wrok around iam stopping the the cluster sender channel at remote end and starting it... the same is done at our end also restarting the cluster receiver channel...then the files are moving.....But this type of solution doesnt solve our purpose......
Can anyone please help me out in the issue............
We are using Windows platform.
When i checked the logs getting the folloing error..
AMQ9558: Remote Channel is not currently available.
EXPLANATION:
The channel program ended because the channel 'RBINGP_RCHNL' is not currently
available on the remote system. This could be because the channel is disabled
or that the remote system does not have sufficient resources to run a further
channel.
ACTION:
Check the remote system to ensure that the channel is available to run, and
retry the operation. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Apr 27, 2010 12:19 am Post subject: Re: MQ Cluster Sender Channel going into retrying state |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| tsantoshkumar wrote: |
| ...Recently due to some problem, we have shifted the Machine(full repository). I have taken the QManager backup and restored the same in new machine... |
And followed the manual in regard to 'moving' a Full Repository, which effectively you have done?
| tsantoshkumar wrote: |
| ...some of the QM(3) are not able to send the files properly. The cluster sender channel at remote is going into retrying mode... |
Would these CLUSSDR's be the ones to the FR you 'moved'?
| tsantoshkumar wrote: |
...When i checked the logs getting the folloing error..
AMQ9558: Remote Channel is not currently available.
EXPLANATION:
The channel program ended because the channel 'RBINGP_RCHNL' is not currently
available on the remote system. This could be because the channel is disabled
or that the remote system does not have sufficient resources to run a further
channel.
ACTION:
Check the remote system to ensure that the channel is available to run, and
retry the operation. |
Check everything in the queue managers having the issue, and also the 'RBINGP_RCHNL' in the receiving queue manager; follow the manual for fault finding and how to resolve issues such as these.
Remember, your FR now is NOT the same queue manager as the one before. It may have the same name, it may have the same named objects, it may have the same IP Address and IP Port, but it is NOT the same queue manager and you need to ensure that all the other queue managers in the cluster know that!
_________________
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 |
|
|
| PeterPotkay |
| Posted: Tue Apr 27, 2010 5:03 am Post subject: Re: MQ Cluster Sender Channel going into retrying state |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| exerk wrote: |
| Remember, your FR now is NOT the same queue manager as the one before. It may have the same name, it may have the same named objects, it may have the same IP Address and IP Port, but it is NOT the same queue manager and you need to ensure that all the other queue managers in the cluster know that! |
I guess it depends what kind of backup was done. Server backup and restore - then it still has the same QMID. MS03 backup and rebuild- then its a different QM (with the same name).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Apr 27, 2010 5:25 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| tsantoshkumar wrote: |
| ...We are using Windows platform... |
I wonder how the back-up was taken? Was it a VM? Ghost? However, you do make a fair point and with much better clarity than I did 
_________________
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 |
|
|
| Sam Uppu |
| Posted: Tue Apr 27, 2010 7:21 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Once I had this issue by copying the backup from one box and trying to replay on a new queue manager/ new box. I forgot to change the ip of the clusrcvr channel.
See the following URL:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzah.doc/qc13100_.htm
The scenario could be bad ip in the clusrcvr channel. At the first time, when you start the channel, it will start with ip address provided in clussdr channel. After disconnect interval (default 6000 sec), it will start with the ip provided in clusrcvr channel. Please double check your config.
Thanks. |
|
| Back to top |
|
|
| tsantoshkumar |
| Posted: Tue Apr 27, 2010 10:02 pm Post subject: |
|
|
Apprentice
Joined: 10 Mar 2008
Posts: 26
|
Hi,
The backup process i have followed is :
I have taken the backup of qmgr folder for the exisiting machine.
In the new machine I have created the Queue Manager with same name and same port as in previous machine. Stopped the QM. Then I have replaced the qmgr folder with the backup taken. Started the QManager.
Regards,
Santosh |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Apr 27, 2010 10:46 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Then it is not the 'same' queue manager as previously; did you issue RESET CLUSTER(<cluster name>) ACTION(FORCEREMOVE) QMID(<original qmid>) QUEUES(YES) on the other FR?
EDIT: You did of course record the QMID's of all your queue managers in the cluster?
_________________
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 |
|
|
| tsantoshkumar |
| Posted: Wed Apr 28, 2010 2:58 am Post subject: |
|
|
Apprentice
Joined: 10 Mar 2008
Posts: 26
|
Hi,
I have checked with the QMID of both the QManagers(original and backup). They are having same QMID.
Regards,
Santosh. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 28, 2010 3:14 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| tsantoshkumar wrote: |
| ...Then I have replaced the qmgr folder with the backup taken... |
Doh! Note to self, read the whole post!
Did IP's change? Or any other settings within channel/queue manager objects? The fact that you are having to restart CLUSRCVR channels is a little suspicious.
_________________
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 |
|
|
| tsantoshkumar |
| Posted: Wed Apr 28, 2010 5:33 am Post subject: |
|
|
Apprentice
Joined: 10 Mar 2008
Posts: 26
|
Hi,
The IP's of the machine has changed.But we have natted the IP with common 12.x.x.x series. We are connecting the channels using the 12 series IP.
Earlier we have natting as folows:
182.x.x.11 -- 12.x.x.x
182.x.x.14-- 12.x.x.x
Same natting IP has been given though internal IP is different.
Regards,
Santosh. |
|
| Back to top |
|
|
|
|
