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 Discussion » ZX0000001 and HL066062 queue manager fails to start

Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next
 ZX0000001 and HL066062 queue manager fails to start « View previous topic :: View next topic » 
Author Message
ankurlodhi
PostPosted: Thu May 23, 2013 10:46 am    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

there were no messages on the queue when the Queue Manager was shut down as it was activity of after production hours.

Vitor can you Put some light on the dodge you have mentioned i never read any post on them.
Back to top
View user's profile Send private message
Andyh
PostPosted: Thu May 23, 2013 11:45 am    Post subject: Reply with quote

Master

Joined: 29 Jul 2010
Posts: 239

A queue manager cannot run with only 1 recovery log.

When was this queue manager last running ?
If the queue manager has been running since the last tape backup it is extremely unlikely that restoring the 'missing' log files from tape will help.

A cold start might be your best option here.
It's not a supported operation, but if you've lost the recovery logs it might be your best option. MQ should be able to talk you through this procedure, and any other steps needed to recover (for example resolving any associated indoubts and channels).

In the event of a queue manager restart failure then pretty much the first thing that should be done is to take a backup of the queue manager data and recovery logs. If nothing else, this will allow MQ support to investigate the reason for the restart failure (not applicable in this case).
Back to top
View user's profile Send private message
ankurlodhi
PostPosted: Thu May 23, 2013 12:05 pm    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

Andyh can you provide me with steps how to cold start MQ.
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu May 23, 2013 12:09 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ankurlodhi wrote:
there were no messages on the queue when the Queue Manager was shut down as it was activity of after production hours.


It's a well designed WMQ system that has no messages on any queue once the day's processing is done. And a very confident man that's sure it's always the case.

ankurlodhi wrote:
Vitor can you Put some light on the dodge you have mentioned i never read any post on them.


Start here and accept that this is not point in time recovery, just a way to get your queue manager running.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu May 23, 2013 12:38 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

and if the qmgr is part of a cluster, it's better to do a cold-start than to delete it and rebuild it.

if the qmgr is not part of a cluster, it's better to delete it and rebuild it.
Back to top
View user's profile Send private message
ankurlodhi
PostPosted: Thu May 23, 2013 12:52 pm    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

vitor this was a planned activity for which an outage was taken and box was taken down after making an information, actually it was a CPU fan replacement, so whole box was taken.

so yes i am very confident there was no msg in anyqueue anywhere ..
Back to top
View user's profile Send private message
ankurlodhi
PostPosted: Thu May 23, 2013 1:11 pm    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

the queue manager is not a part of any cluster but since we have asked for the Tapes i will wait for them and restore the MQ file system. if that doesn't work i will recreate it.
Back to top
View user's profile Send private message
ankurlodhi
PostPosted: Thu May 23, 2013 1:13 pm    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

will this work on version 5.3

As well as anything works on 5.3 any more
Back to top
View user's profile Send private message
ankurlodhi
PostPosted: Fri May 24, 2013 6:33 am    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

Thanks for the Advise everyone i got the Queue manager running but i might need some more help i will seek it when i need it.

as of now queue manager is running but

channels are in going in Retrying state one channel was running a few minutes ago but now it's not working
may be there is a problem on the other side.
Back to top
View user's profile Send private message
ankurlodhi
PostPosted: Fri May 24, 2013 8:15 am    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

we are getting this error from the mainframe side

CSQX500I *MQA CSQXRESP Channel MQM.PPWEB2.TO.MQSA started

+CSQX632I *MQA CSQXRESP SSL certificate has no associated user ID, 133

remote channel MQM.PPWEB2.TO.MQSA

connection sbkprdprtweb2 (::ffff:192.168.172.92)

- channel initiator user ID used

+CSQX526E *MQA CSQXRESP Message sequence error for channel 137

MQM.PPWEB2.TO.MQSA, sent=40663 expected=40665

+CSQX599E *MQA CSQXRESP Channel MQM.PPWEB2.TO.MQSA ended abnormally
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri May 24, 2013 9:03 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ankurlodhi wrote:
+CSQX526E *MQA CSQXRESP Message sequence error for channel 137

MQM.PPWEB2.TO.MQSA, sent=40663 expected=40665


Says it all. The queue manager did have messages in it when you brought it down.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Fri May 24, 2013 9:13 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Vitor wrote:
ankurlodhi wrote:
+CSQX526E *MQA CSQXRESP Message sequence error for channel 137

MQM.PPWEB2.TO.MQSA, sent=40663 expected=40665


Says it all. The queue manager did have messages in it when you brought it down.


The SNDR/RCVR channel pair could have been inactive at Sequence Number 40665 and then one end was restored to an older point in time. This by itself wouldn't be proof there were messages in flight or even waiting in the XMITQ.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri May 24, 2013 9:15 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

PeterPotkay wrote:
Vitor wrote:
ankurlodhi wrote:
+CSQX526E *MQA CSQXRESP Message sequence error for channel 137

MQM.PPWEB2.TO.MQSA, sent=40663 expected=40665


Says it all. The queue manager did have messages in it when you brought it down.


The SNDR/RCVR channel pair could have been inactive at Sequence Number 40665 and then one end was restored to an older point in time. This by itself wouldn't be proof there were messages in flight or even waiting in the XMITQ.


Good point. The OP did talk about a restore.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
ankurlodhi
PostPosted: Fri May 24, 2013 9:55 am    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

i didn't restored the queue manager i followed the instructions provided in link given by vitor after that ..

the Reveiver channels and Listening from my end which is on solaris
but there is this errors on mainframe side.

what can we do to fix it. as i am not handling MQ over mainframe.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri May 24, 2013 9:58 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.

ankurlodhi wrote:
what can we do to fix it. as i am not handling MQ over mainframe.

What do the mainframe support people say?
_________________
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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next Page 2 of 3

MQSeries.net Forum Index » General Discussion » ZX0000001 and HL066062 queue manager fails to start
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.