ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Corrupt SYSTEM.AUTH.DATA.QUEUE

Post new topic  Reply to topic
 Corrupt SYSTEM.AUTH.DATA.QUEUE « View previous topic :: View next topic » 
Author Message
chrisc
PostPosted: Sun Jul 20, 2008 10:26 pm    Post subject: Corrupt SYSTEM.AUTH.DATA.QUEUE Reply with quote

Voyager

Joined: 19 Mar 2006
Posts: 77

Hi there,

One of our queue managers (it's a repository QM in a cluster, if that makes any difference) has managed to get a corrupted SYSTEM.AUTH.DATA.QUEUE.

I realise that this is what stores all the access control lists for MQ, so I'm not really sure what the implications are in terms of security with this QM now... but that's not really my question now.

Is it safe to delete and recreate this queue? Actually, is it necessary or is there another way? (The strmqm with RDEFSYS(*YES) command apparently won't do anything for corrupt queues, in fact it doesn't even touch this particular queue at all.)

Assuming I do this, do I have to reissue all the setmqaut commands to reapply the necessary security on this QM? I'm guessing that this is pretty likely, in order to repopulate the queue.

Thanks,
Chris
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Jul 21, 2008 6:44 am    Post subject: Re: Corrupt SYSTEM.AUTH.DATA.QUEUE Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

chrisc wrote:
Hi there,

One of our queue managers (it's a repository QM in a cluster, if that makes any difference) has managed to get a corrupted SYSTEM.AUTH.DATA.QUEUE.

I realise that this is what stores all the access control lists for MQ, so I'm not really sure what the implications are in terms of security with this QM now... but that's not really my question now.

Is it safe to delete and recreate this queue? Actually, is it necessary or is there another way? (The strmqm with RDEFSYS(*YES) command apparently won't do anything for corrupt queues, in fact it doesn't even touch this particular queue at all.)

Assuming I do this, do I have to reissue all the setmqaut commands to reapply the necessary security on this QM? I'm guessing that this is pretty likely, in order to repopulate the queue.

Thanks,
Chris
Well if you are running in linear logging you could always try to recover the queue from media.

Otherwise I guess you will have to delete it, recreate it and reissue the setmqaut commands.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
AkankshA
PostPosted: Mon Jul 21, 2008 8:05 pm    Post subject: Re: Corrupt SYSTEM.AUTH.DATA.QUEUE Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore

In case you do not ahve linear logging and intend to recreate the queue the i would suggest use strmqm -c option..

i.e. first delete the queue manually
Stop the QM
and then issues strmqm -c <QMName>
strmqm <QMName>

strmqm -c ll recreate the missing system objects for you...
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
chrisc
PostPosted: Mon Jul 21, 2008 9:23 pm    Post subject: Reply with quote

Voyager

Joined: 19 Mar 2006
Posts: 77

Thanks for the suggestion AkankshA. I'll make a note of that.

Although now I'm thinking it may be totally fine anyway...!

The current MQ environment here needs quite a bit of work, and it still has a mixture of MQ v5 and v6. The QMs in question are MQ v6, but the MQ Explorer I was using when I first looked was for v5.3. I know that you shouldn't use different MQ Explorer versions to the QM version, but it had already been added to the list and I just clicked on it!

Basically the MQE5.3 shows it as damaged, but runmqsc does not. It's not showing up at all in MQE6, and I initially thought this meant it was REALLY corrupted, but now I think that it's because we have applied security to these QMs to have read-only access via MQE.

I've read somewhere that the SYSTEM.AUTH.DATA.QUEUE has all sorts of special restrictions on non-mqm users doing stuff, even with setmqaut run against it, so I think MQE6 must be omitting it for that reason, not because it's corrupt.

(And yes, I have strongly recommended to the client that they get on with upgrading all their MQ to v6! )

Anyway, thanks for the info, I'll keep it in mind for if/when it ACTUALLY gets corrupted!
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Corrupt SYSTEM.AUTH.DATA.QUEUE
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.