| Author |
Message
|
| mvarghese |
 Posted: Wed Jan 21, 2009 8:40 am Post subject: QMGR messages to new QMGR |
 |
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
One of the QMGR (5.3) which is part of cluster(PR) running on windows server has an issue to retriveing information from FR,even though cluster SDR channel, RCVR channel ruuning fine & no SYSTEM.TEMP.QMGR etc.So we are unable to put message in cluster q's.(remote QMGR cluster q's are not visible from here).
Togther around a million messages are on different q's in this QMGR which is unable to send via cluster channels to differnt QMGR.
So we recreated another Queue Manger on another box,but the question is how we are able to move the old QMGR q messages to new QMGR with out any loss of messages.We don't have any tool to do this.
In window's any chance to copy the directory structure which have q's(dspmqfls) and moved to new QMGR.Is it workable solution.Any one tried this..any better suggestion..
Note:Please Don't respond by saying..read document/pdf..
_________________
Jain Varghese |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jan 21, 2009 8:48 am Post subject: Re: QMGR messages to new QMGR |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mvarghese wrote: |
| In window's any chance to copy the directory structure which have q's(dspmqfls) and moved to new QMGR.Is it workable solution. |
No it's not.
| mvarghese wrote: |
any better suggestion..
|
Use the q or qload applications (both support pacs or maybe now in a single pac?) to unload the messages from where they are and reload them onto the new queue manager. Depending on the number of queues involved you might want a touch of scripting.
Simple, supported, works a treat.
Other solutions are undoubtably possible.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvarghese |
| Posted: Wed Jan 21, 2009 9:33 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Thanks Vitor.
Just need few more info about q tool.
Based on past few times we used, q or qload is unable to retrieve the MQMD header, so it only copy the messages ..so information in the header like reply to Q and reply to QMGr all lost.
But header able to copy using a seperate commmand .But not seen single command copying the header with data.
_________________
Jain Varghese |
|
| Back to top |
|
|
| dkeister |
| Posted: Wed Jan 21, 2009 10:18 am Post subject: |
|
|
Disciple
Joined: 25 Mar 2002
Posts: 184
Location: Purchase, New York
|
try MQExerciser...
_________________
Dean Keister |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jan 21, 2009 10:27 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mvarghese wrote: |
| ...Based on past few times we used, q or qload is unable to retrieve the MQMD header, so it only copy the messages... |
Extracted from the MO03 documentation:
"...The default action of the WebSphere MQ Queue Load / Unload Utility is to set all the context information in the MQMD to that which was saved in the file being loaded. This requires the user ID under which the utility is running to have appropriate authority to set all the context fields..."
"...The fields in the Message Descriptor (MQMD) are formatted in the file with a three character string representing the attribute name. “Table 7: Message descriptor attribute representations” lists the full set of these strings and which field they represent..."
The MQMD's should be preserved...
_________________
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 |
|
|
| SAFraser |
| Posted: Wed Jan 21, 2009 10:32 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I use qload to write messages to a file on disk, then FTP the file elsewhere, then use qload to load the file to a queue. The headers have always been preserved.
As Vitor said, works a treat. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 21, 2009 11:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mvarghese wrote: |
Based on past few times we used, q or qload is unable to retrieve the MQMD header, so it only copy the messages ..so information in the header like reply to Q and reply to QMGr all lost.
|
The qload utility does copy the MQMD. It's formatted as show in Table 7 here and is treated according to the context options on reload.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Wed Jan 21, 2009 2:20 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| mvarghese wrote: |
Thanks Vitor.
Just need few more info about q tool.
Based on past few times we used, q or qload is unable to retrieve the MQMD header, so it only copy the messages ..so information in the header like reply to Q and reply to QMGr all lost.
But header able to copy using a seperate commmand .But not seen single command copying the header with data. |
You may try WMQTool with which you can copy the msgs from a queue and write to a file and also you can route the msgs from one QMgr to the other. |
|
| Back to top |
|
|
| mvarghese |
| Posted: Wed Jan 21, 2009 3:07 pm Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Thanks every one for giving the right info.
_________________
Jain Varghese |
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Jan 21, 2009 5:14 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
| I am interested in why the problem happened. Can share the cause of the problem if it's been found? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 21, 2009 5:37 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
99% of cluster problems are either network problems or channel definition problems.
If you think recreating the QM on another server is going to help, more power to you, but unless you have identified the problem as being related to the hardware on the original , all you are likely doing is recreating the QM on another server and moving the problem with it.
Before you go thru all the trouble of moving these messages, did you test the new QM in the cluster to prove it works? Did you recreate the new QM with the same name as the old? If yes, have you ejected the old one from the cluster?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mvarghese |
| Posted: Thu Jan 22, 2009 9:25 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
1:The windows server which used in one of the MQ Adapter is quite not stable in terms of harware configuration.They alerday had a plan to migrate to new Hardware.
2.The old box, QMGR is not getting any cluster information from full repostiory..tried all methods ..but no result..
Since its production, other box set up ready on the very next day.
3.But we recreate the old QMGR in old box,it able to get cluster FR information...so some wrong happened with QMGR.(Cirular logging..small size they created quite long time back).To make sure that it was QMGR issue.
_________________
Jain Varghese |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jan 22, 2009 12:14 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| 99% of cluster problems are either network problems or channel definition problems. |
Hmmm.
I would have said that 99% of cluster problems are due to sysadmins not understanding how to manage a cluster - self-inflicted wounds. This inludes inappropriae use of mqsc cluster commands and altering/deleting cluster object definitions.
The WMQ Clusters manual is a wealth of knowledge, and contains how-to's for creating clusters, adding and removing cluster qmgrs from a cluster, altering cluster object definitions, and use of cluster commands.
_________________
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 |
|
|
|
|
