| Author |
Message
|
| saitotnk |
 Posted: Wed Apr 09, 2008 4:28 pm Post subject: unable to remove damaged qremote |
 |
|
Newbie
Joined: 09 Apr 2008
Posts: 2
|
Hello,
First time I'm posting on this forum, I hope I post in the right area. I ran into a strange problem, I googled a little bit without finding the answer. I'm unable to delete a qremote on one of my MQ server.
runmqsc <QUEUE_MANAGER>
delete qremote('SOME_REMOTE_QUEUE')
1 : delete qremote('SOME_REMOTE_QUEUE')
AMQ8101: WebSphere MQ error (893) has occurred.
[1012, 20]
AMQ8101: WebSphere MQ error (893) has occurred.
display qremote('SOME_REMOTE_QUEUE')
2 : display qremote('SOME_REMOTE_QUEUE')
AMQ8149: WebSphere MQ object damaged.
my /var/mqm/qmgrs/<QUEUE_MANGER>/errors/*.log does not tell me anything when I execute this command.
I also did following
rcrmqobj -m <QUEUE_MANGER> -t qr <SOME_REMOTE_QUEUE>
AMQ7044: Media recovery not allowed.
Can someone point me towards right direction? I would like to remove it if it's damage.
Here is a little info
MQ Server 6.0
Solaris 9 Generic_118558-39
Thanks,  |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Apr 09, 2008 9:16 pm Post subject: Re: unable to remove damaged qremote |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| saitotnk wrote: |
display qremote('SOME_REMOTE_QUEUE')
2 : display qremote('SOME_REMOTE_QUEUE')
AMQ8149: WebSphere MQ object damaged.
The object is damaged, if you want to confirm it again, use sageqmgr support pac tool (MS03), and execute, it will also prompt you if there are some damaged objects.
my /var/mqm/qmgrs/<QUEUE_MANGER>/errors/*.log does not tell me anything when I execute this command.
I suspect some one played with the queue manager file system,
by mistake deleted the queue files
I also did following
rcrmqobj -m <QUEUE_MANGER> -t qr <SOME_REMOTE_QUEUE>
AMQ7044: Media recovery not allowed.
if its linear log, then only you can think of media recovery.
Here is a little info
MQ Server 6.0
Upgrade to 6.0.2+
|
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| saitotnk |
| Posted: Thu Apr 10, 2008 6:53 am Post subject: Re: unable to remove damaged qremote |
|
|
Newbie
Joined: 09 Apr 2008
Posts: 2
|
| Gaya3 wrote: |
| saitotnk wrote: |
display qremote('SOME_REMOTE_QUEUE')
2 : display qremote('SOME_REMOTE_QUEUE')
AMQ8149: WebSphere MQ object damaged.
The object is damaged, if you want to confirm it again, use sageqmgr support pac tool (MS03), and execute, it will also prompt you if there are some damaged objects.
|
Regards
Gayathri |
I downloaded saveqmgr, and followed instructions to run saveqmgr.solaris. It provided me a complete configuration dump for my queue manager, as well as a list of damaged objects. I'm a little confused here. Should I delete the entire queue manager, and recreate it from scratch with the output file I got from saveqmgr? Is that my only option here?
I would like to know how remove the damage objects, so I can recreate them in my queue manager.
Thanks,  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 10, 2008 6:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Your queue manager is broken... either at the file system level or even worse.
You can either open a PMR, or recreate the queue manager.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 10, 2008 7:25 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
you can delete just the damaged queue and recreate it with a QM bounce thrown in. I posted the exact steps a while back. You of course lose any messages in the queue, but that's not an issue for a q remote or for an empty local queue.
A damaged q is a very very rare event for a properly set up and administered MQ server. You have bigger issues than just the damamged queue.
I don't know what else is wrong with your set up so this may not get you back 100%.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 10, 2008 7:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PeterPotkay wrote: |
| you can delete just the damaged queue and recreate it with a QM bounce thrown in. |
The delete is failing...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 10, 2008 7:41 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
This is unofficial advice that I haven't done in years. Take it for what its worth. It saved our bacon multiple times until we were able to upgrade MQ.
| Quote: |
1. Schedule an Emergency outage.
2. If this is a Queue Manager in Fail Over mode under MSCS control, leave the Queue Manager’s cluster group where it is.
3. Delete the damaged queue file from the Queue Manager's queue directory in the file system.
4. If this is a Queue Manager in Fail Over mode under MSCS control, have the QM brought down and up by using Microsoft Cluster Service. DO NOT (EVER) BRING DOWN A QM UNDER MSCS CONTROL BY ANY OTHER MEANS (like the command line, or MQExplorer). Otherwise, just bounce the QM normally.
5. Delete the damaged queue using MQExplorer.
6. Recreate the queue via MQExplorer. Refer to previous MS03 backups to make sure you recreate it exactly as it was before.
7. If the damaged queue was a transmit queue, other queue definitions (Remote Queue Defs, QMAliases) were altered to use a temporary backup queue that replaced the damaged queue. Now is the time to alter all those to point back at the real queue you just recreated.
8. If the damaged queue was a transmit queue, alter the channel to refer to the correct transmit queue, and not the temporary backup transmit queue.
9. Close MQExplorer.
10. Have the QM brought down and up (use MSCS if it is a HA QM) to see if the QM is happy with the new queue. Open up MQ Explorer to verify.
11. Send 100+ persistent messages thru this queue, to verify that the channel is correctly using the new queue. DO NOT skip this step. You may find that you need to reset sequence numbers on the channel. If it is a plain local queue that was damaged, just put and get some messages from it, as long as it won’t interfere with an application.
12. Close MQExplorer.
13. If this is a Queue Manager in Fail Over mode under MSCS control, have the cluster group moved back to its primary location. Open up MQExplorer to verify that the QM is still OK with the new queue. Run the Channel Checker scripts (W:\MQ\ChannelChecker\) to verify everything works OK after moving the QM back.
14. Delete the temporary back up queue.
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 10, 2008 7:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I repeat - your step 5 is clearly failing.
| saitotnk wrote: |
delete qremote('SOME_REMOTE_QUEUE')
1 : delete qremote('SOME_REMOTE_QUEUE')
AMQ8101: WebSphere MQ error (893) has occurred. |
I don't see how using PCF from MQExplorer will succeed when runmqsc is failing - given that both runmqsc and the command server bind against the same internal interfaces.
_________________
I am *not* the model of the modern major general.
Last edited by jefflowrey on Thu Apr 10, 2008 2:13 pm; edited 1 time in total |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 10, 2008 11:58 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Jeff, I saw the same thing. But if you delete the q file first, then bounce the QM, it seemed to allow the deletion of the q thru explorer at that point.
Maybe it worked only at my particular version of MQ (5.3.3 or .4 I think) and only on Windows and only on days that ended in y, but we did use the exact procedures outlined here 4 or 5 times successfully.
No guarantees this will fix things or not make them even worse!!!! Just letting saitotnk what we did in a similiar situation.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
