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 » Query - if MQ logs get full

Post new topic  Reply to topic
 Query - if MQ logs get full « View previous topic :: View next topic » 
Author Message
MQ_Lover
PostPosted: Mon Jul 22, 2013 12:59 am    Post subject: Query - if MQ logs get full Reply with quote

Acolyte

Joined: 15 Jul 2013
Posts: 67

Hi All,

I have a general query where by whats the best action to be taken in case we reach the stage of MQ Queue Manager logs getting full. I have never reached this stage in practical experience in my career yet but this is what I have read around. Please advise if this the best approach.

1) Circular or Linear logs getting full

a) If a long unit of work consumes all the log files primary and secondary, as action stop the Queue Manager, increase the number of primary log and secondary log files, considering that the Queue Manager log file system example /MQHA/Qmgr/log can support the equivalent of space.

b) Incase the number of primary and secondary already reached a limit where it matches equivalent to /MQHA/Qmgr/log filesystem get system admins to add more space to filesystem and increase the number of logs files in proportion to match it the new added space.

Thanks
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jul 22, 2013 4:19 am    Post subject: Reply with quote

Poobah

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

Calculating log file size and number of logs is well-documented. Managing logs is well-documented, too.

Where did you read about this? When you read about this, what were the recommendations?
_________________
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
MQ_Lover
PostPosted: Mon Jul 22, 2013 5:42 am    Post subject: Reply with quote

Acolyte

Joined: 15 Jul 2013
Posts: 67

Hi bruce2359,

Thanks for the reply, I have read the IBM documents which in details specifies the Managing the log files, but it doesn't specifies if your logs still get full even after all housekeeping in place what is recommended and how to get out of that situtation, I have read what I have posted somewhere on MQ support sites only, and trying to get best recommended steps from mqseries.net forum as we have so many MQ gurus someone must have faced this situation before. I would have love to experiment with this on my own on a test system but not sure how do I make a never ending transaction to see it for myself.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jul 22, 2013 6:04 am    Post subject: Reply with quote

Poobah

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

Did you also read about calculating log size?
_________________
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
MQ_Lover
PostPosted: Mon Jul 22, 2013 6:35 am    Post subject: Reply with quote

Acolyte

Joined: 15 Jul 2013
Posts: 67

Yep, read it once again as here - http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzae.doc%2Fic12020_.htm but didn't get a answer still to my query
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jul 22, 2013 7:00 am    Post subject: Reply with quote

Poobah

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

That url took me to short retry.
_________________
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
bruce2359
PostPosted: Mon Jul 22, 2013 7:01 am    Post subject: Reply with quote

Poobah

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

If you run out of log space, allocate more.
_________________
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
Vitor
PostPosted: Mon Jul 22, 2013 7:13 am    Post subject: Reply with quote

Grand High Poobah

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

MQ_Lover wrote:
how do I make a never ending transaction to see it for myself.


Write a piece of code with an MQPUT in an infinate loop which never commits any messages.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
MQ_Lover
PostPosted: Mon Jul 22, 2013 8:02 am    Post subject: Reply with quote

Acolyte

Joined: 15 Jul 2013
Posts: 67

@bruce2359 - sorry not sure but for some reason it is doing the same with me also I have pasted the correct one but it take to short retry strange, thanks for your input.

Hi Vitor - thanks, I will try to do that.
Back to top
View user's profile Send private message
Andyh
PostPosted: Mon Jul 22, 2013 10:38 am    Post subject: Reply with quote

Master

Joined: 29 Jul 2010
Posts: 239

Log full in a circular logging environment indicates that the longest running transaction has such a long duration that the logs approach wrapping before that transaction completes. When this situation arises the queue manager will unilaterally rollback the oldest active transaction.

I would strongly advise that rather than increase the size of the log you investigate the reason for the long running transaction.
To some extent the duration of the longest running transaction determines the amount of transaction replay/rollback required at queue manager crash restart. If you consume very big circular logs then you are potentially at risk of long restart times.

MQ V7.5 enhances the dspmqtrn command to make it easier to detect and monitor long running transactions.
Back to top
View user's profile Send private message
MQ_Lover
PostPosted: Tue Jul 23, 2013 12:33 am    Post subject: Reply with quote

Acolyte

Joined: 15 Jul 2013
Posts: 67

Hi Andy - Great, thanks for making me aware on this good point, defintely something to keep in mind before increasing the log files, thanks again.
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 Discussion » Query - if MQ logs get full
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.