Author |
Message
|
basa_bbc |
Posted: Tue Jan 20, 2004 1:50 am Post subject: Log Full |
|
|
Apprentice
Joined: 20 Jan 2004 Posts: 35
|
Hi ,
We have used circular logging in mq series , i have increased the Secondary log file count also to maximum . now both primary and secondary have got count of 62 .
But at this stage also when the messages being received , mq is throwing an exception "Log file full ".
I have already increased it to the maximum . Circular logging should rewrite the previous logs , but its not doing so .
could anybody please help me ASAP regarding this issue .
Advance thanks ,
bbc |
|
Back to top |
|
 |
JasonE |
Posted: Tue Jan 20, 2004 2:43 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
One normal cause is a channel in doubt - Check your channels. Long running UOW's can cause this problem, but I think (not sure) that they get backed out when log space is running low, so its a long running prepared transaction. Do you use any XA coordination, if so try dspmqtrn -e.
Circular logging will only reuse old log files when they are not in use. One head meets tail, you get this error. |
|
Back to top |
|
 |
basa_bbc |
Posted: Tue Jan 20, 2004 2:49 am Post subject: |
|
|
Apprentice
Joined: 20 Jan 2004 Posts: 35
|
Hi jason,
Thanx for the reply ,
We are not using any xa transaction . my channels are also not in-doubt state . The program is a normal program which puts the message onto the queue . i have put 500 kb message of 1000 numbers .
Its taking almost 3 min to pass a message to its destination , and i am getting the log full error on the receiver end .
I am not sure as to why even in circular logging after 52 log files have been created the head is not meeting the tail .
could u pls give a solution to this ASAp |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Jan 20, 2004 6:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If the log files on the receiving size of a channel are too small to hold the full batch size, you will get issues like this. If this is the case then to fix this, you need to actually reduce the batch size. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
pgorak |
Posted: Wed Jan 21, 2004 4:07 am Post subject: |
|
|
 Disciple
Joined: 15 Jul 2002 Posts: 158 Location: Cracow, Poland
|
What is the size of your single log file? Remember that contrary to primary and secondary settings, you can't increase log file size by simply editing the settings and restarting the queue manager.
Piotr _________________ ***
IBM Certified Solution Developer WebSphere MQ 5.3 |
|
Back to top |
|
 |
basa_bbc |
Posted: Wed Jan 21, 2004 4:15 am Post subject: |
|
|
Apprentice
Joined: 20 Jan 2004 Posts: 35
|
Hi ,
The log size of each file is 1024 KB . i.e 256pages * 4KB . |
|
Back to top |
|
 |
pgorak |
Posted: Wed Jan 21, 2004 4:34 am Post subject: |
|
|
 Disciple
Joined: 15 Jul 2002 Posts: 158 Location: Cracow, Poland
|
Perhaps you just need more. You could compute these requirements given the log space consumed by each MQSeries operation (in the manuals) and the characterisic of your environment. You need to know how much log space is consumed before you make 10000 logged operations.
This matter has actually been discussed here, I guess more than once. Let me know if you need more information.
Piotr _________________ ***
IBM Certified Solution Developer WebSphere MQ 5.3 |
|
Back to top |
|
 |
Carla Viragh |
Posted: Wed Jan 21, 2004 5:01 am Post subject: |
|
|
 Voyager
Joined: 31 Oct 2003 Posts: 92 Location: São Paulo - Brasil
|
pgorak wrote: |
Perhaps you just need more. You could compute these requirements given the log space consumed by each MQSeries operation (in the manuals) and the characterisic of your environment. You need to know how much log space is consumed before you make 10000 logged operations.
This matter has actually been discussed here, I guess more than once. Let me know if you need more information.
Piotr |
I agree... If I understood, QM receiver has a log space (total) of 52MB but it´s not enough for 1000 * 0,5MB. Is it the scene? And as you have just said, it´s important to compute the MQ space requirements for each action (log overhead sizes). _________________ Carla Viragh |
|
Back to top |
|
 |
pgorak |
Posted: Wed Jan 21, 2004 5:34 am Post subject: |
|
|
 Disciple
Joined: 15 Jul 2002 Posts: 158 Location: Cracow, Poland
|
I'd suggest the following approach: say I perform 1 GET and 1 PUT in one UOW and then I perform commit (which is a very simple case and does not include operations performed by channel agents).
1. Using the log overhead sizes, compute the average overhead per operation - let's name this A
2. 10000 operations will consume 10000 times A of space
3. Then, choose a logfilesize and see how many files (i.e. primary files) you need to provide the space calculated in step 2.
4. And obviously, round the value up and add one extra primary file
Piotr _________________ ***
IBM Certified Solution Developer WebSphere MQ 5.3 |
|
Back to top |
|
 |
Carla Viragh |
Posted: Wed Jan 21, 2004 8:51 am Post subject: |
|
|
 Voyager
Joined: 31 Oct 2003 Posts: 92 Location: São Paulo - Brasil
|
Yes, always add space, MQ never uses all the log space available because it needs space to backout (if necessary). So, it could be in error even if there´s space! _________________ Carla Viragh |
|
Back to top |
|
 |
Neysa |
Posted: Thu Jan 22, 2004 4:46 am Post subject: |
|
|
Newbie
Joined: 28 Nov 2002 Posts: 7 Location: Netherlands
|
You say both primary and secundary logfiles have a count of 62, I asume you mean you have 62 primary logfiles AND 62 secundary logfiles?
Because this won't work, the max for the number of primary logfiles is 62 and for secundary logfiles is 61, however the sum of both can't exceed 63.
I've never tried to set a higher numberthan 63 total, but I would expect an error when restarting the queuemanager if you do. But you don't mention this, so did you restart the queuemanager after setting this number?
And is the underlying filesystem large enough? |
|
Back to top |
|
 |
|