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 IndexGeneral IBM MQ SupportCircular logs

Post new topicReply to topic
Circular logs View previous topic :: View next topic
Author Message
GregJ
PostPosted: Mon Nov 05, 2001 2:11 pm Post subject: Reply with quote

Acolyte

Joined: 24 Oct 2001
Posts: 69
Location: Markham, On. Canada

We receive the message amq7469 (Transactions rolled back due to log space). we have increased the log sizes, but still receive the error.

Also, we have noticed that when viewing the logs - they aren't all there (started with 20, now have 12).

Question:
How do we 'release' the log? How can we tell which transcation is killing us?

any info will help greatly
Back to top
View user's profile Send private message
bduncan
PostPosted: Mon Nov 05, 2001 4:33 pm Post subject: Reply with quote

Padawan

Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley

You mention that some of the log files are no longer there. How many of your cirular logs are primaries, and how many are secondaries? This could explain why you are seeing fluctuation in the number of log files. Secondaries are utilized and released as necessary, while primaries are always allocated a preset amount of disk space. In terms of "releasing" logs, I'm not sure if you are refering to a queue manager marking a particular section of log as being available for overwriting, or removing the log files themselves. Either way, you cannot control this yourself, the queue manager does this housekeeping automatically. In terms of making sure that logs are being reused, your applications must always commit or backout any transactions. In terms of secondaries being removed, the queue manager does this when the amount of load on the system that caused the secondaries to be created in the first place has subsided. And primaries are never removed from disk.


_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
Back to top
View user's profile Send private message Visit poster's website AIM Address
GregJ
PostPosted: Tue Nov 06, 2001 7:20 am Post subject: Reply with quote

Acolyte

Joined: 24 Oct 2001
Posts: 69
Location: Markham, On. Canada

May have an answer for myself - will let you know if it turns out to be true :

I changed the log parameters in the mqs.ini, then deleted and recreated the queue manager.

After the queue manager was created, I deleted the new queue manager folder and copied in the old queue manager folder (which contained all my definitions). In my old queue manager folder, the qm.ini still had my old log settings, while the mqs.ini contained the new ones.

Since the mqs.ini had 10 primaries (which displayed in the logs folder), and the old mq.ini had 3 primaries... I am assuming that once the 10 disappearing logs reaches 3, it will become circular again....

does this make any sence at all? And thank you very much for your help.
Back to top
View user's profile Send private message
bduncan
PostPosted: Tue Nov 06, 2001 12:42 pm Post subject: Reply with quote

Padawan

Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley

I think you have the right idea, but your statement:
"I am assuming that once the 10 disappearing logs reaches 3, it will become circular again.... "

is a bit confusing. If you define your queue manager logs as circular, they will always be circular. Take the following scenario:
1. I have 3 primaries. I start doing MQSeries operations that require use of the logs. The queue manager starts writing to the first log. At some point my unit of work ends, and the queue manager marks that section of logs as being free to be overwritten. At the same time, new units of work may be started, but they won't use the space freed up from the first unit of work. The queue manager will continue to use the first log file until it reaches the end, and then start on the second. Again, it will not go back and use space that has been freed up - it will always continue forward. That is, until it reaches the end of the third log. Now it will loop back to the first log file and start writing on top of the old information, assuming that it has been marked for overwriting. If it hasn't been marked for overwriting yet, then we have a problem. The queue manager will attempt to create a secondary (assuming you configured your qm.ini file to allow this). If a secondary is created, you will now have 4 log files, and after reaching the end of the third file, instead of looping back to #1 (because #1 is still in use) it will proceed on to the secondary which is considered #4. When it reaches the end of this secondary, the same check is performed. If the beginning of log file has been marked for overwriting, it will loop back to #1, otherwise, create another secondary. If it cannot loop back to #1, nor create another secondary (because it has exhausted them) then the queue manager will give the error you saw, saying that it has exhausted the log space....


_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
Back to top
View user's profile Send private message Visit poster's website AIM Address
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportCircular logs
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.