| Author |
Message
|
| Rahul999 |
 Posted: Wed Jun 16, 2010 4:51 am Post subject: Can we delete Queue Mgr without Impacting Message Broker? |
 |
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Hi All,
Is it possible to delete the Broker Queue Manager without deleting/impacting the broker. The queue manager we are currently having is generating lot of FDC's, we are not able to come up with a fast resolution even after looking at FDC's.
For a quick solution, we want to delete and recreate the queue manager(obviously using the SaveQmgr utility first to save and later to restore MQ objects)
well , the point is
1. We have one queue manager which is shared by both config manager and Message Broker, what would be the impact if we delete this queue manager and create a new queue manager with the same name and restoring/recreating back all the MQ objects(including the broker related Queues and channels)??
2. As both Broker and ConfigMgr store their information in different repositories which is un-related to any of MQ files. so I think that deleting a queue manager would not impact those directories. Please confirm this point.
Message MQ version is - 6.0.2.8 , OS is - AIX, Broker Version is V6.1
Regards, |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Jun 16, 2010 4:59 am Post subject: Re: Can we delete Queue Mgr without Impacting Message Broker |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| Rahul999 wrote: |
Is it possible to delete the Broker Queue Manager without deleting/impacting the broker. The queue manager we are currently having is generating lot of FDC's, we are not able to come up with a fast resolution even after looking at FDC's.
For a quick solution, we want to delete and recreate the queue manager(obviously using the SaveQmgr utility first to save and later to restore MQ objects)
well , the point is
1. We have one queue manager which is shared by both config manager and Message Broker, what would be the impact if we delete this queue manager and create a new queue manager with the same name and restoring/recreating back all the MQ objects(including the broker related Queues and channels)??
2. As both Broker and ConfigMgr store their information in different repositories which is un-related to any of MQ files. so I think that deleting a queue manager would not impact those directories. Please confirm this point.
Message MQ version is - 6.0.2.8 , OS is - AIX, Broker Version is V6.1
Regards, |
i dont think its a good idea, i am not sure, how it impacts, even if you think about Cold - Start Procedure too. it may create some problems to to event pub-sub messages.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 16, 2010 5:15 am Post subject: Re: Can we delete Queue Mgr without Impacting Message Broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Rahul999 wrote: |
| Is it possible to delete the Broker Queue Manager without deleting/impacting the broker. |
No.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Wed Jun 16, 2010 5:19 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Gaya3 wrote:
| Quote: |
| dont think its a good idea, i am not sure, how it impacts, even if you think about Cold - Start Procedure too. it may create some problems to to event pub-sub messages. |
To highlight it further , this queue manager was recently started with the cold start procedure, what actually happened was we accidentally deleted some of the queue manager S Logs and then to start the queue manager we have to create a dummy queue manager and copy its Log and Control file to our queue manager and then we managed to start the queue manager, but now its giving lot of problem, specially related to configuration manager.
There are lot of FDC's files are being generated where all of them are having many probe ID's, it starts like this -
| Quote: |
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday June 16 14:45:29 SGT 2010 |
| Host Name :- barb020c (AIX 5.3) |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.8 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- HL062051 |
| Application Name :- MQM |
| Component :- mqlCreateExtent |
| SCCS Info :- lib/logger/amqherr0.c, 1.19.1.1 |
| Line Number :- 118 |
| Build Date :- Sep 30 2009 |
| CMVC level :- p600-208-090930 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000008 (abcmq) |
| Program Name :- amqzmuc0 |
| Addressing mode :- 64-bit |
| Process :- 1581152 |
| Thread :- 4 |
| QueueManager :- BRK_QM |
| ConnId(1) IPCC :- 5 |
| ConnId(2) QM :- 6 |
| Last HQC :- 2.0.0-330936 |
| Last HSHMEMB :- 2.10.11-1270176 |
| Major Errorcode :- hrcE_MQLO_ACCD |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 113639 |
there are few more FFS similar to above and later the FFS changes to what shown below
| Quote: |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday June 16 14:45:30 SGT 2010 |
| Host Name :- barb020c (AIX 5.3) |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.8 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- HL006004 |
| Application Name :- MQM |
| Component :- hlgWriteLogRecord |
| SCCS Info :- lib/logger/amqhlgw0.c, 1.26.1.1 |
| Line Number :- 399 |
| Build Date :- Sep 30 2009 |
| CMVC level :- p600-208-090930 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000008 (abcmq) |
| Program Name :- amqzmuc0 |
| Addressing mode :- 64-bit |
| Process :- 1581152 |
| Thread :- 7 |
| QueueManager :- BRK_QM |
| ConnId(1) IPCC :- 14 |
| ConnId(2) QM :- 12 |
| Last HQC :- 2.0.0-438984 |
| Last HSHMEMB :- 2.8.8-191632 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- hrcE_MQLO_ACCD |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20806822) |
| FDCSequenceNumber :- 113641 |
| Arith1 :- 545286178 20806822 |
| |
And similarly there are more FFS's with Probe Ids as
| Quote: |
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday June 16 14:45:33 SGT 2010 |
| Host Name :- barb020c (AIX 5.3) |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.8 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- AL018001 |
| Application Name :- MQM |
| Component :- almReserveSpace |
| SCCS Info :- lib/lqm/amqalme0.c, 1.21.1.2 |
| Line Number :- 388 |
| Build Date :- Sep 30 2009 |
| CMVC level :- p600-208-090930 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000008 (abcmq) |
| Program Name :- amqzmuc0 |
| Addressing mode :- 64-bit |
| Process :- 1581152 |
| Thread :- 7 |
| QueueManager :- BRK_QM |
| ConnId(1) IPCC :- 14 |
| ConnId(2) QM :- 12 |
| Last HQC :- 2.0.0-438984 |
| Last HSHMEMB :- 2.8.8-191632 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- hrcE_MQLO_UNEXPECTED_OS_ERROR |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20806716) |
| FDCSequenceNumber :- 113705 |
| Arith1 :- 545285910 20806716 |
| |
and so on ..
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Wed Jun 16, 2010 6:21 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Rahul999 wrote:
| Quote: |
| Is it possible to delete the Broker Queue Manager without deleting/impacting the broker. |
vitor wrote:
Hi Vitor,
May I know what would be the impact, does broker wouldn't allow queue manager to be deleted without deleting it first?
Regards, |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Jun 16, 2010 6:36 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Broker keeps QMGRID in its repositiory...... 
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Wed Jun 16, 2010 6:56 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
gaya3 wrote:
| Quote: |
| Broker keeps QMGRID in its repositiory.. |
Holy shit.. that is something.
Well, then closing this case, can you guide me about the FDC's problem we are facing with MQ as I mentioned earlier.
Seems like resolving the MQ FDC's problem is an only alternative.
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 16, 2010 7:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Rahul999 wrote: |
| can you guide me about the FDC's problem we are facing with MQ as I mentioned earlier. |
What did IBM say when you raised the PMR?
Have you tried another, more careful, cold start? Or retrieving the deleted log files off a system backup?
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Wed Jun 16, 2010 7:05 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 16, 2010 7:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It looks like you're having disk issues or capacity issues creating log files. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Jun 16, 2010 9:55 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 16, 2010 10:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You wouldn't expect to need to change kernel settings on a box where the queue manager was already running & had just had an unfortunate incident really 
Likewise with capacity or disk issues you wouldn't really expect that if you'd just cold started with new, identical logs. Of course, if you've cold started with different size or number of logs then that could be a problem, hence my comment about doing it again & more carefully. Accidents happen, especially when you're rushing to fix a problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Blomman |
| Posted: Wed Jun 16, 2010 10:53 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Hi!
I have done it on Version 5.3, someone deleted all the qmgrs S*LOGs...
We just deleted it and all directorys, recreated the directorys and recreated the qmgr with the same....
Everything kept running without any problems....
Then we switched platform and went to WMB 7.0.1...
//Blomman |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Wed Jun 16, 2010 11:00 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Gaya3 wrote:
above link was not helpful as it is valid for Solaris and MQ V5.3, whereas we are running MQ V6.0 on AIX operating system. Anyway thanks for your help.
vitor wrote:
| Quote: |
You wouldn't expect to need to change kernel settings on a box where the queue manager was already running & had just had an unfortunate incident really
Likewise with capacity or disk issues you wouldn't really expect that if you'd just cold started with new, identical logs. Of course, if you've cold started with different size or number of logs then that could be a problem, hence my comment about doing it again & more carefully. Accidents happen, especially when you're rushing to fix a problem. |
Yes, I missed out the part(to bring no of primary and secondary log files in sync with our queue manager) while creating the dummy queue manager. I followed the cold start procedure again with keeping everything in sync.
thanks vitor for pointing me in the correct direction.
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
|
|
|
