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 » URGENT!! Unique Sender Error

Post new topic  Reply to topic Goto page Previous  1, 2
 URGENT!! Unique Sender Error « View previous topic :: View next topic » 
Author Message
Vitor
PostPosted: Wed Oct 10, 2007 2:09 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
yea, 5.0 in prod.


I admire your nerve. I wouldn't have taken the job.....

insertcoin wrote:

I have already tried that command. Its something like this:

RESOLVE CHSTATUS(channelName) ACTION(BACKOUT)

and... I tried to commit too... nothing.


Again with the nerve. Though I wonder at the reasoning of trying both backout and commit...

insertcoin wrote:
So you are suggesting I stop the Command Server and then restart it?


I'm inclinded to agree with the estemed jefflowrey that a more comprehensive stop/start may be the way forward. Even if it's production, this is a major failure and downtime is inevitable.

Not convinced how much there is to recover if you've resolved by backout the channels, but IIRC the Cressida tool reads log files. Hope it reads v5.0 format ones.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 2:53 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

Ok, so I spoke to our CTO and he told me that we need to back up these messages before we start stopping the networking services.

So, whats the best way for me to back up these messages?
Yes, they are persistent, but with this ancient 5.0 version... anything is possible!

Help?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Oct 10, 2007 3:11 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

...

You can't take a valid backup of a running MQ, particularly one that old.

If you have messages sitting on a queue, and you know that they are not uncommitted (you can see them with a browse), then you can use any number of free or trial tools to back up the messages into a flat file. Popular choices include M071 and CapitalWare's MQVisualEdit.

If the messages are UNCOMMITTED, you don't see them with amqsbcg, for examples, then you can't do anything to back them up without stopping the queue manager.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 3:39 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

I dont know if you can call it nerve, I think I was actually tricked into taking this job!

I tried both, because the one never worked, and there were no messages on the queue at that time. Meaning, if I commit nothing or backout nothing, then nothing can get lost! It was reckless I admit, but things arent going to well around here.

I tried an amqsget on my local machine, piped it to a text file... then piped it back and that worked... However, if the message is too long then you get a 2080 error, something about truncated message. It makes sense.

So... what was the link to the free trial app or something?

They even suggested that I copy paste the message from the data tab...
but if the amqsget isnt going to get the whole message, I know that neither will this method!

What I can do, looking at the browse command... is pipe the browsed info into a text file JUST for recording purposes... then bring MQ down and try do what I can?! Im going to test on local, and then check back here with you legends!

Thanks alot for the input guys!
Really really might be saving a mans job today!
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 3:41 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

Ok, the browse into a txt file works!

Now, how do I get that info back onto the queue, should that be necessary?
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 3:46 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
I tried both, because the one never worked, and there were no messages on the queue at that time. Meaning, if I commit nothing or backout nothing, then nothing can get lost! It was reckless I admit, but things arent going to well around here.


What queue? If it's a channel problem they'd be on the xmitq, possibly uncommitted and invisible.

insertcoin wrote:

So... what was the link to the free trial app or something?


MO71 is a support pac available from the IBM site (doesn't suffer from the length issue of amqs* apps, which are only samples anyway).

You'll find Capitalware's fine product at:

www.capitalware.biz
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 3:48 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
Ok, the browse into a txt file works!

Now, how do I get that info back onto the queue, should that be necessary?


If you mean amqsbcg, it's not a browse command but a sample program. The output doesn't pipe back.

Use MO71, which comes with instructions. Or VisualEdit.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 4:05 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

... the other sender channel went down again

The error message for that was a pop up window that complained about the command server not responding within the timeout period.

So, POA is to find MO17 and backup the messages, then stop MQ and restart the Command server... if that doesnt work we will probably bounce the prod box after hours, which Im not too keen on doing.

Thanks guys.

Oh, and by Queue... I meant XMITQ, sorry about not being down with the jargon! I know it makes it harder to explain things!
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 4:11 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

Product categories:
Software
Business Integration
Application Integration and Connectivity
WebSphere MQ
SupportPac
Operating system(s):
Windows
Software version:
5.1, 5.2, 5.3, 6.0
Reference #:
4000142
IBM Group:
Software Group
Modified date:
2007-05-18



5.1...... is the earliest.

We dont have any other box that has 5.0 on it, so I cant test... unless I test on PROD?! .... I might suck at what I do, but I know that that isnt the smartest thing to do.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Oct 10, 2007 4:14 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It shouldn't break the queue manager if it doesn't work. It just might not work.

Same with VisualEdit.

The other thing to consider is if it's okay to merely use amqsbcg output as a "backup". You should presumably be able to get enough information from that to give to the sending applications so that they can resubmit the same data.

That's a question for your CIO and for the sending app teams.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 4:25 am    Post subject: Reply with quote

Grand High Poobah

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

jefflowrey wrote:
You should presumably be able to get enough information from that to give to the sending applications so that they can resubmit the same data.

That's a question for your CIO and for the sending app teams.


You should certainly plan for the contingency that the data sent is unrecoverable in whole or part, and will need to be reconstructed by the sending application, possibly by a manual process involving reconciliation with the receiving end.

And when your CTO complains how much this is costing the business, remind him of all the money he's saved not upgrading MQ for all these years.

And smile.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 5:52 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

MO71 just saved my freaking life!

... well, it could have! Its still a good application though... Ill be using it more frequently no doubt!

I backed up all the messages, which didnt need to be.
The persistent messages stayed on the xmitq so I didnt need to load them back again.

Steps taken:
1)consult legends on mqseries.net
2)backup'd important xmit queues
3)stopped MQ service
4)attempted to bring it back online... failed.
5)restart the box.
6)open MQ once the server came back up.
7)cheer and celebrate... all while planning for the next time that sh!7 hits the fan!

Something to do with the network TCP stack that got too full.
All better now!

Much appreciated Guys!
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 6:00 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
7)cheer and celebrate... all while planning for the next time that sh!7 hits the fan!


Start upgrading to supported version of MQ, or at least less whiskered / buggy / contact admin / unstable version
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Oct 10, 2007 6:04 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Vitor wrote:
insertcoin wrote:
7)cheer and celebrate... all while planning for the next time that sh!7 hits the fan!


Start upgrading to supported version of MQ, or at least less whiskered / buggy / contact admin / unstable version


And consider a Unix platform...
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 6:09 am    Post subject: Reply with quote

Grand High Poobah

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

jefflowrey wrote:
Vitor wrote:
insertcoin wrote:
7)cheer and celebrate... all while planning for the next time that sh!7 hits the fan!


Start upgrading to supported version of MQ, or at least less whiskered / buggy / contact admin / unstable version


And consider a Unix platform...


Goes without saying....
_________________
Honesty is the best policy.
Insanity is the best defence.
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 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » URGENT!! Unique Sender Error
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.